SQL Server MCP

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

28/28 tools missing one or more hints — connect (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); disconnect (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_connections (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +25 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.

Descriptions match behaviour

2 tools describe read intent but their handlers mutate — export_to_json (line 66: with open(path, "w", encoding="utf-8") as f:); export_to_csv (line 138: path.write_text(""))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

19/28 tool handlers declare input schemas (68%)

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

Tool handlers catch errors

27/28 tool handlers wrap calls in try/catch (96%)

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

export_to_json: description implies read-only but handler writes/deletes/executes; export_to_csv: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.