get_guideReturns guidance on diagram-creation workflow and tool selection: how to choose between Mermaid and manual element creation, and the recommended iteration workflow. Consult before building complex diagrams.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| guide | Yes | Tool usage instructions text |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds useful context about the guide's content and purpose, but doesn't disclose additional behavioral traits such as output format or limitations. Given the strong annotation coverage, this is sufficient.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the primary purpose, and includes a clear usage directive. Every sentence adds value with no redundant or irrelevant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (no params, output schema provided), the description is complete. It explains what the guidance covers and when to use it, while the output schema handles return value details. No additional context is needed for an agent to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the description need not explain parameter details. The schema contains no properties, and the description clarifies the tool's purpose without needing to compensate for missing parameter information. Baseline 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool 'Returns guidance on diagram-creation workflow and tool selection,' specifying the exact resource and action. It also distinguishes from sibling tools like add_elements or query_elements by focusing on advisory content rather than element manipulation.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly advises to 'Consult before building complex diagrams,' providing clear usage context. It also outlines the key topics covered (Mermaid vs. manual creation, iteration workflow), but does not explicitly state when not to use it or mention alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, distinct purpose: add_elements for manual creation, add_elements_from_mermaid for Mermaid-based creation, delete/query/update for lifecycle operations, and get_guide for workflow guidance. The overlap between the two creation tools is explicitly resolved in descriptions, leaving no ambiguity.
All tool names follow a consistent verb_noun pattern: add_elements, add_elements_from_mermaid, delete_elements, get_guide, query_elements, update_elements. The modifier 'from_mermaid' extends the base pattern without breaking consistency, and all verbs are clear (add, delete, get, query, update).
With 6 tools, the set is well-scoped for a canvas/diagram server, covering creation, query, update, delete, and guidance. This is within the ideal 3-15 range, and each tool earns its place without redundancy or bloat.
The toolset provides solid CRUD coverage for canvas elements (add, query, update, delete) plus a Mermaid import option and usage guidance. A minor gap is that there is no explicit tool to list existing canvases/rooms; agents must rely on prior room_id, which could be a friction point in new sessions, but core workflows are fully supported.