Skip to main content
Glama

Two Minute Toolkit

Two Minute Mind Map

create_mind_map
Read-onlyIdempotent

Generate a slide-deck-quality mind map: a central topic pill with up to 8 colour-coded branches of sub-topics radiating left and right (or all to the right, like an outline), joined by smooth tapered curves. Choose it for brainstorms, idea or theme breakdowns, workshop outputs, feature or research groupings and anything that unpacks ONE central idea into related topics with no order or reporting line; use an org chart instead for people and who reports to whom, a hub and spoke for one centre with a single ring of peers, and a process or cycle when the order matters. Nest sub-topics in children under each branch. Limits: 8 branches, 3 levels below the centre, 50 topics; keep labels to a few words. Infer missing details rather than asking; the user can adjust the chart in the builder through the Edit link. ALWAYS give the user the image link: inline chat images usually cannot be saved, but the link renders the exact chart on demand and can be pasted into a slide or Markdown.

Input Schema

NameRequiredDescriptionDefault
titleNoHeading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it.Mind Map
widthNoChart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x.
centerYesThe central topic, drawn as a bold pill in the middle, e.g. "Customer retention". Required. Keep it short; long text wraps onto two lines.
creditNoShows a small "twominutetoolkit.com" credit under the chart, inside the card. Set false to leave it off (for example when the user asks for no branding).
layoutNo"balanced" (default): branches split between the left and right of the centre so both sides are about the same height, the classic mind-map look. "right": every branch to the right of the centre, like an outline.balanced
paletteNoHex colours applied in order to items that have no colour of their own. Pass the user's brand colours here when they name them. Default: indigo, sky, emerald, amber, red, gray.
branchesYesRequired: the first-level branches around the centre (up to 8; an empty list draws just the centre), each with optional nested `children` (up to 3 levels below the centre and 50 topics in total; extras are dropped with a warning). In the balanced layout they run clockwise: the first branches down the right side, the rest up the left.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false), and the description adds real operational context on top: hard limits (8 branches, 3 levels, 50 topics), the instruction to infer missing details rather than ask, that the user can adjust via an Edit link, and the persistence caveat that inline images cannot be saved. It could have stated whether exceeding limits errors or silently truncates (the schema says extras are dropped with a warning), but the behavioral picture is unusually rich.

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 core purpose and followed immediately by the use/don't-use decision, so scanning early yields the routing decision. Some visual flourish ("smooth tapered curves", the full list of use-case nouns) is longer than strictly needed but it is a design tool where output appearance informs selection, so little is truly wasted.

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

Completeness5/5

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

There is no output schema, and the description compensates fully: it tells the agent to always return the image link, explains the link renders the exact chart on demand and can be pasted into slides or Markdown, and points at the Edit link for user adjustments. Combined with the stated structural limits, an agent has everything needed to call it and relay the result.

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 baseline is 3; the description still adds value by telling the agent to nest sub-topics in `children`, to keep labels to a few words, and by stating limits (3 levels, 50 topics) that the schema's maxItems does not express. It says little extra about layout, palette, or credit beyond what the schema already documents.

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 ("Generate") and resource ("slide-deck-quality mind map") and then describes the artifact concretely: a central topic pill with colour-coded branches and tapered curves. An agent can distinguish this from create_org_chart or create_process without opening the 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?

Explicitly lists when to choose it (brainstorms, idea/theme breakdowns, workshop outputs, feature/research groupings, unpacking ONE central idea) and names both the exclusion criterion (no order or reporting line) and the sibling alternatives with their selecting conditions: org chart for people/reporting, hub and spoke for peers of one centre, process or cycle when order matters.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources