PC Controller 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

38/38 tools missing one or more hints — config_get (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); config_set (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_usage_stats (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +35 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 749 (fs.rm(targetPath, { recursive: recursive || false, force: recursive || false }))

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

Only 5/38 tool handlers declare input schemas (13%)

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

Tool description accuracy

file_edit: description implies read-only but handler writes/deletes/executes

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