list_saved_diagramsList auto-saved diagrams from earlier sessions, newest first, with their pages. Resume any diagram by passing its session ID to start_session.
List the diagrams saved by earlier sessions (auto-save files), newest first, with their pages. Continue one with start_session session_id=; the file path also works with load_diagram.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: results are derived from auto-save files, are ordered newest first, and carry their pages. It does not disclose whether there is a cap or pagination, which keeps it at 4 rather than 5.
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?
Two sentences, no filler, and the identifying facts (auto-save, newest first, with pages) come before the continuation advice. Every clause carries information an agent needs.
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?
With no output schema, the description compensates by stating what each entry contains and its ordering, and it explains how to act on the results. It omits anything about result volume or truncation, which is a minor remaining gap for a list tool.
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 takes zero parameters, so the baseline is 4. The only parameter-like detail mentioned (session_id=<id>) belongs to start_session, and the description correctly frames it as the continuation mechanism rather than an argument to this call.
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?
Specific verb (List) + resource (saved diagrams), plus the qualifying scope that this is about auto-save files from earlier sessions, not live diagrams. It also names the ordering (newest first) and the returned unit (with their pages), which cleanly separates it from list_pages and get_diagram.
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?
It routes the agent onward with concrete alternatives: continue a listed item via start_session session_id=<id>, or reach the same file through load_diagram. That is explicit next-step guidance with a named parameter. It stops short of stating when NOT to use this tool (e.g. to find the currently open diagram), so it falls just under a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.