Grimmory MCP Server

Tool annotations

4/52 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

48/52 tools missing one or more hints — grimmory_list_authors (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); grimmory_get_author (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); grimmory_find_author_by_name (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +45 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

openWorldHint matches behaviour

4 tools claim openWorldHint=false but make outbound HTTP — grimmory_list_libraries → libraries (line 47); grimmory_get_library → dynamic (line 81); grimmory_list_shelves → shelves (line 55)

Either flip openWorldHint to true (acknowledging external reach) or refactor the handler to avoid outbound HTTP. If the only network calls are to a known fixed endpoint that you consider part of the tool itself, document that and keep openWorldHint=false; otherwise true is honest.

Tool inputs are validated

Only 0/52 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/52 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tests pass

npm test failed — tests do not pass

Make sure npm test runs cleanly. Common cause: missing build step or missing env vars.