Use Case
When configuring the toolkit with the MATLAB MCP core server (--extension-file=tools/tools.json), the six Simulink tools load successfully, but they are advertised to MCP clients with no annotations. As a result, clients fall back to the MCP spec defaults, treating every tool as potentially destructive and non‑idempotent.
The annotations appear to have already been thoughtfully authored in tools/registry.json (readOnlyHint, destructiveHint, idempotentHint, openWorldHint for all six tools). However, this is not the file the MCP server reads. Every setup guide (README.md, GETTING_STARTED.md, claude-code-setup-guidance.md, etc.) points --extension-file at tools.json.
Relevant Skill or MCP Tool
Add MCP annotations to tools.json
Proposed Behavior
It would be great, and aligns with best practice, if the annotations in registry.json could be reviewed and added across to tools.json.
Current Workaround
No response
Additional Context
No response
Use Case
When configuring the toolkit with the MATLAB MCP core server (--extension-file=tools/tools.json), the six Simulink tools load successfully, but they are advertised to MCP clients with no annotations. As a result, clients fall back to the MCP spec defaults, treating every tool as potentially destructive and non‑idempotent.
The annotations appear to have already been thoughtfully authored in tools/registry.json (readOnlyHint, destructiveHint, idempotentHint, openWorldHint for all six tools). However, this is not the file the MCP server reads. Every setup guide (README.md, GETTING_STARTED.md, claude-code-setup-guidance.md, etc.) points --extension-file at tools.json.
Relevant Skill or MCP Tool
Add MCP annotations to tools.json
Proposed Behavior
It would be great, and aligns with best practice, if the annotations in registry.json could be reviewed and added across to tools.json.
Current Workaround
No response
Additional Context
No response