Skip to main content
Glama

Two Minute Cycle Diagram

create_cycle
Read-onlyIdempotent

Generate a slide-deck-quality cycle diagram: 3–8 stages evenly spaced around a loop, first stage at 12 o'clock running clockwise, joined by arrows that lead from the last stage back to the first, with an optional centre label and a short detail line beside each stage. Two looks: "nodes" (coloured circles on a ring with curved arrows) and "segments" (a ring cut into arrow-shaped segments). Choose it when the process repeats: improvement loops (plan-do-check-act), flywheels, product or customer lifecycles, feedback loops. Use a process diagram instead when steps run once from start to finish, a timeline when dates matter, and hub and spoke when the items surround a centre with no order. Limits: 3–8 stages, 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": {
      "style": "nodes",
      "title": "Continuous improvement loop",
      "center": "Customer value",
      "stages": [
        {
          "name": "Plan",
          "detail": "Set the quarter's bets"
        },
        {
          "name": "Build",
          "detail": "Ship small, ship often"
        },
        {
          "name": "Measure",
          "detail": "Track usage and outcomes"
        },
        {
          "name": "Learn",
          "detail": "Keep what works, drop what doesn't"
        }
      ]
    },
    "name": "create_cycle"
  }
}

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
styleNo"nodes" (default): coloured circles on a ring joined by curved arrows, stage names inside the circles. "segments": a thick ring cut into coloured arrow-shaped segments, stage names outside.nodes
titleNoHeading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it.Cycle
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.
centerNoOptional label in the middle of the loop, e.g. the goal the cycle serves ("Customer value"). Bold, wrapped to up to 3 lines. Omit for 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).
stagesYesThe stages in order (3–8). The first sits at 12 o'clock and the loop runs clockwise, back from the last stage to the first. Fewer than 3 still render but are reported as a warning; more than 8 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.

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.6/5.0
Behavior4/5

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

Annotations only say readOnly/idempotent/closed-world, so the description carries real weight here: it discloses soft limits (3–8 stages, 1–3 word names, ~12 word details), the degradation behavior for too few or too many stages, the builder Edit link for user adjustment, and the non-obvious output-handling rule that inline chat images can't be saved so the link must be given. It does not describe latency or what the returned payload looks like (URL, dimensions), which keeps it off 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?

One dense paragraph, front-loaded with what it produces, then looks, routing, limits, and workflow. Every clause is actionable, though the limits line partly duplicates the schema's minItems/maxItems and the final ALWAYS-link sentence is long enough to risk being skimmed.

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?

With 8 parameters all documented in the schema and no output schema, the description supplies the missing pieces an agent needs: routing against siblings, ordering semantics, content-length expectations, and what to hand back to the user (the image link, not an inline embed). Nothing required for a correct invocation is left unstated.

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 description coverage is 100%, so baseline is 3; the description still adds semantic value beyond it by explaining the ordering convention (first stage at 12 o'clock, loop runs clockwise, last links back to first) and the intended granularity of names and details. The 'regular/bold/sketch' look is only enumerated in the schema, so the description doesn't fully restate parameter behavior.

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 opening sentence names a specific verb (Generate) and a precise resource (slide-deck-quality cycle diagram), then enumerates the visual contract: 3–8 stages, 12 o'clock start, clockwise, closing arrow, optional centre label, per-stage detail line. It explicitly carves itself out from create_process, create_timeline and create_hub_spoke, so an agent can route correctly without opening sibling schemas.

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 triggers (repeating processes: PDCA, flywheels, product/customer lifecycles, feedback loops), explicit negative routing with the reason for each alternative (process diagram for one-pass steps, timeline when dates matter, hub and spoke for unordered items around a centre), plus operating guidance: infer missing details rather than asking, and always surface the image link.

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