Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "center": "Customer retention",
      "branches": [
        {
          "name": "Onboarding",
          "children": [
            {
              "name": "Setup wizard"
            },
            {
              "name": "Templates"
            }
          ]
        },
        {
          "name": "Support",
          "children": [
            {
              "name": "Live chat"
            }
          ]
        },
        {
          "name": "Pricing"
        }
      ]
    },
    "name": "create_mind_map"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookNoDrawing style, the same in every tool. "regular": clean lines and Inter (the default). "bold": heavier, slightly larger type and thicker lines, for slides read from a distance. "sketch": hand-drawn, with a handwriting font and pen lines that wobble a little, for early ideas and workshops. Use the one the user asks for; otherwise leave it out.regular
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. Changed1 schema field changed
    • addedInput schema / properties / look
      Added value: +{
      +  "default": "regular",
      +  "description": "Drawing style, the same in every tool. \"regular\": clean lines and Inter (the default). \"bold\": heavier, slightly larger type and thicker lines, for slides read from a distance. \"sketch\": hand-drawn, with a handwriting font and pen lines that wobble a little, for early ideas and workshops. Use the one the user asks for; otherwise leave it out.",
      +  "enum": [
      +    "regular",
      +    "bold",
      +    "sketch"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered by structured data. The description adds real value beyond that — structural limits (8 branches, 3 levels, 50 topics), the fact that extras are silently dropped with a warning, and the instruction to always surface the image link because inline chat images cannot be saved. It does not describe render time, failure modes, or what an error looks like, so it is solid but not exhaustive.

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 verb and output, then selection rules, then constraints, then the image-link directive — a logical order with no filler sentences. It is dense and long-ish as a single block, and the visual styling details partly duplicate the schema, which keeps it from a 5.

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?

With no output schema, the description correctly explains the return artifact (an image link that renders the exact chart on demand) and how to present it in chat, slides or Markdown. Limits and the drop-extras behavior are stated, which is what an agent needs to build valid input, though error handling and the response shape beyond the link are not spelled out.

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

Parameters3/5

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

Schema coverage is 100%, so every parameter including layout, palette, look, credit and width is already documented in the schema, making 3 the baseline. The description reinforces the nesting pattern ('Nest sub-topics in `children` under each branch'), the 'all to the right, like an outline' reading of the right layout, and label brevity, but adds little that the schema does not already say.

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 artifact ('Generate a slide-deck-quality mind map') and then describes the exact visual structure — a central pill, up to 8 colour-coded branches, tapered curves, balanced or right-side outline layout. It explicitly distinguishes itself from org chart, hub and spoke, and process/cycle, so an agent can select it 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?

Gives positive selection cases (brainstorms, theme breakdowns, workshop outputs, feature/research groupings, unpacking ONE central idea) and explicit when-not cases with the named alternatives (org chart for reporting lines, hub and spoke for a single peer ring, process/cycle when order matters). It also tells the agent to infer missing details rather than asking, which removes a common stall path.

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