Skip to main content
Glama

Two Minute Hub and Spoke

create_hub_spoke
Read-onlyIdempotent

Generate a slide-deck-quality hub and spoke diagram: a large central hub circle with 3–10 coloured satellite cards evenly spaced around it, each joined to the hub by a spoke, with an optional short detail beside each satellite and optional arrowheads (out from the hub, or both ways). Choose it when several items relate to one centre with no order between them: a platform and its products or integrations, a team and its stakeholders, a core value and its pillars, a company and its partners. Use a cycle when the items form a repeating sequence, a process diagram for one-way steps, a mind map when the satellites branch further, and an org chart for reporting lines. Limits: 3–10 spokes, one level only, names of 1–3 words, details of about 12 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": {
      "hub": "Core platform",
      "title": "Platform ecosystem",
      "arrows": "none",
      "spokes": [
        {
          "name": "Mobile app",
          "detail": "iOS and Android"
        },
        {
          "name": "Partner API"
        },
        {
          "name": "Analytics"
        },
        {
          "name": "Billing"
        }
      ]
    },
    "name": "create_hub_spoke"
  }
}

Input Schema

NameRequiredDescriptionDefault
hubYesLabel of the central hub, e.g. "Core platform". Bold white text in a large circle, wrapped to up to 3 lines; 1–4 words reads best.
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.Hub and Spoke
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.
arrowsNoArrowheads on the spokes: "none" (default, plain connecting lines), "out" (from the hub towards each satellite, e.g. distribution or influence), "both" (two-way exchange).none
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).
spokesYesThe satellites around the hub (3–10), placed clockwise from 12 o'clock. Order only decides placement; nothing implies a sequence. Fewer than 3 still render but are reported as a warning; more than 10 are dropped.
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.
hubColorNoOptional hex colour of the hub circle. Default: the first palette colour (indigo #4f46e5), with the spokes taking the following palette colours.

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.3/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 agent knows this is a safe, deterministic generator. The description adds genuinely useful behavioural context: it tells the agent to infer missing details rather than ask, that the user can adjust the chart via an Edit link, and that the image link must always be surfaced because inline chat images usually cannot be saved. It does not describe rendering latency, failure modes, or what happens when the 10-spoke cap is exceeded (that detail lives only in the schema), keeping it short of a 5.

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?

The most important information, what the tool draws and when to choose it, is front-loaded, and the limits and link instruction follow logically. It is a single dense paragraph rather than a structured list, so the limits and the image-link rule are harder to scan than they should be, and a sentence or two could be tightened.

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?

There is no output schema, and the description compensates by explaining what the return (image link) is and why it must be shared, plus the Edit link for adjustments. Combined with full schema coverage and clear annotations, an agent has everything needed to call the tool and present the result, though it never states the response shape or error behaviour explicitly.

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 schema baseline is already a 3. The description still adds semantic framing beyond the schema: it explains that arrowheads encode distribution/influence ('out') versus two-way exchange ('both'), restates the practical content limits (3–10 spokes, one level, names of 1–3 words, details of ~12 words), and explains that spoke order only decides placement and implies no sequence. That is real added meaning, not repetition.

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?

The description opens with a concrete verb and resource ('Generate a slide-deck-quality hub and spoke diagram') and immediately specifies the visual structure: a hub circle with 3–10 coloured satellites, spokes, optional details and arrowheads. That is enough for an agent to tell it apart from create_cycle, create_mind_map, or create_org_chart without opening any 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?

It states the selection condition explicitly ('several items relate to one centre with no order between them') with four concrete examples, then names four exclusions with the conditions that select them: cycle for repeating sequences, process for one-way steps, mind map for further branching, org chart for reporting lines. This is about as complete as when-to-use guidance gets.

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