Skip to main content
Glama

Two Minute Toolkit

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.

Input Schema

NameRequiredDescriptionDefault
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. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover the read-only/idempotent profile, and the description goes well beyond: hard limits (3–8 stages, 1–3 word names, ~12 word details), the degradation behavior implied by those limits, the instruction to infer missing details rather than ask, and the post-call obligation to always surface the image link because inline images are not saveable. That is exactly the operational context an agent cannot get from structured fields.

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 visual spec and then routing, limits and the image-link rule in a logical order. It is dense at roughly 150 words with several long clauses, but nearly every sentence carries distinct information; only the image-link sentence sits oddly inside a tool description.

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?

For a 7-parameter generative tool with no output schema, the description supplies the missing return-value information (an image link plus an Edit link into the builder), the visual contract, and the constraints. Nothing an agent needs to call it correctly or to report results back is absent.

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 description coverage is 100%, so every parameter including style, center, palette and stage detail already carries rich documentation. The description restates the ordering semantics and length guidance that the schema already spells out, adding little new parameter-level meaning beyond the constraints summary.

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 ("Generate a slide-deck-quality cycle diagram") and immediately specifies the geometry: 3–8 stages, 12 o'clock start, clockwise, closing arrow. The two style variants ("nodes" vs "segments") are named, so an agent can distinguish this from create_process, create_timeline and create_hub_spoke 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?

Explicit when-to-use clause ("Choose it when the process repeats") with concrete examples: PDCA loops, flywheels, lifecycles, feedback loops. It also names the three sibling alternatives and the condition that selects each (process for one-way steps, timeline when dates matter, hub and spoke for unordered items around a centre).

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