Skip to main content
Glama

Show a diagram

visualize

Turn long text or ideas into structured diagrams—mind maps, flowcharts, org charts, timelines, fishbones, swimlanes, or outlines—directly in chat.

Instructions

Show an idea to the user as a diagram instead of a long text. Pick the structure from what the content is: exploring a topic -> mindmap; a hierarchy or parts of a whole -> org or logic; steps and decisions -> flowchart; causes of a problem -> fishbone; events in order -> timeline; who does what -> swimlanes (give lanes, and a lane on each node); a long list to read top to bottom -> outline. Rules: labels of 1-5 words; 3-7 children per node; at most 3 levels and about 30 nodes at first; put detail in note. Give every node a short id. For a tree set parent on every node but the root. For a flowchart leave parent out and join the nodes with edges; label the edges out of a decision. The first node is the root or the start. Send no positions and no colors. To show a diagram again, pass only its docId. To change one that is on screen, use edit_diagram, not this tool.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "visualize"
  }
}

Input Schema

NameRequiredDescriptionDefault
docIdNoAlone: show that diagram again. With nodes: replace it.
edgesNoFlow between flowchart nodes, or cross links between tree nodes
lanesNoSwimlanes only
nodesNoEvery idea or step, root or start first. Needed for a new diagram.
themeNoLeave out unless the user asked for a look. host follows the chat client.
titleNoShort title of the diagram
animateNoLeave out unless the user asked. Default: on.
structureNoHow to draw it. Pick from what the content is; the user can switch later.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint=false, so the agent knows this mutates state, and the description adds the key behavioral detail that passing docId with nodes replaces an existing diagram. It also states constraints the schema cannot express (no positions, no colors, node/level limits, detail belongs in note). It stops short of saying what the call returns, which matters because docId is the handle for re-showing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and the structure-selection heuristic, then a compact 'Rules:' block, so the most decision-relevant content comes first. It is dense and longer than typical, but nearly every clause carries operational weight; only the repeated sizing hints could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter creation tool with no required fields and no output schema, the description covers structure choice, node/edge topology rules, and when to defer to edit_diagram, which is enough to call it correctly. The remaining gap is return behavior: it never says the response yields the docId that the re-show path depends on.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning beyond the schema: how nodes vs edges differ per structure, that swimlanes require lanes plus a lane on each node, that parent is omitted for flowchart nodes, and that the first node is the root or start. That is real interpretive guidance rather than repetition of field docs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('show an idea to the user as a diagram instead of a long text') and immediately enumerates the structures it can render. It explicitly distinguishes itself from the sibling edit_diagram ('to change one that is on screen, use edit_diagram, not this tool'), so an agent can route without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit content-to-structure mapping (exploring a topic -> mindmap, steps and decisions -> flowchart, events in order -> timeline) plus when to use alternatives: edit_diagram for on-screen changes, docId-only for re-showing. Exclusions and the alternative are named, not inferred.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.