Freya MCP Server

Tool annotations

No tools have read-only/destructive annotations

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

All four hints declared on every tool

180/180 tools missing one or more hints — read_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); write_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); delete_file (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +177 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.

Destructive tools are labelled

1 tool perform destructive updates without destructiveHint — delete_file deletes at line 499 (fsp.rm(abs, { recursive: true, force: true }))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Tool inputs are validated

96/112 tool handlers declare input schemas (86%)

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

Tool handlers catch errors

Only 10/112 tool handlers wrap calls in try/catch (9%)

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

Tool test coverage

Only 8/180 tools referenced in tests (4%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

4 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.