Skip to main content
Glama

Two Minute Chevron Process

create_process
Read-onlyIdempotent

Generate a slide-deck-quality chevron process diagram: 2–7 phases drawn as arrow-shaped chevrons left to right, each with an optional timing line ("Weeks 1–2") and up to 5 short bullets beneath it, and an optional "you are here" highlight on one phase. Choose it for an "our approach" or methodology slide, delivery phases, a sales or onboarding process, or any short linear sequence where the ORDER of the phases matters; use a timeline instead when exact dates and overlapping durations matter, a cycle diagram when the last step loops back to the first, and an org chart or mind map for branching structures. Limits: 2–7 steps, up to 5 bullets per step; keep step names to one to three words and bullets to a short phrase. 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": {
      "steps": [
        {
          "name": "Discover",
          "timing": "Weeks 1–2",
          "bullets": [
            "Stakeholder interviews",
            "Current-state audit"
          ]
        },
        {
          "name": "Design",
          "timing": "Weeks 3–5",
          "bullets": [
            "Target architecture",
            "Prototype"
          ]
        },
        {
          "name": "Build",
          "timing": "Weeks 6–12"
        },
        {
          "name": "Launch",
          "timing": "Week 13"
        }
      ],
      "title": "Our delivery approach",
      "current": 1
    },
    "name": "create_process"
  }
}

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
stepsYesThe phases, left to right (2–7; extra steps are dropped with a warning). Each step is one chevron with its name inside, an optional timing line just under it and optional bullets beneath. Keep names to one to three words; long names shrink, wrap to two lines, then truncate.
titleNoHeading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it.Our Approach
widthNoChart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height is computed from the content.
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).
currentNoOptional highlight: the 0-based index of one step (0 is the first step). A pointer with a label (currentLabel, default "You are here") appears above that step; every step keeps its colour. Omit for no highlight (the default).
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.
currentLabelNoText above the pointer on the highlighted step (only shown when current is set). Default "You are here"; e.g. "We are here", "Today", "Current phase".You are here

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.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered; the description adds genuinely new operational behavior: infer missing details rather than asking, the user can adjust via the builder Edit link, and the agent must always surface the image link because inline chat images cannot be saved. That last point is valuable context beyond structured fields, though it stops short of describing failure behavior or what happens when the 2–7 limit is violated (the schema hints at a warning but the description does not).

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 artifact and its visual anatomy, then usage routing, then limits, then the image-link instruction — a sensible order. It is delivered as one dense paragraph, and the limits sentence slightly duplicates the schema's min/max, which keeps it from a 5.

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 an 8-parameter generation tool with no output schema, the description covers what is produced, what the hard limits are, how to handle underspecified input, how the user edits afterwards, and how to hand the result back as a link. An agent has everything needed to call it correctly and to present 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 the baseline is 3; the description adds meaning on top by tying the step shape to the parameters (name inside the chevron, optional timing line under it, up to 5 short bullets beneath, one "you are here" highlight on a phase) and by giving style advice (one to three words for names, short phrases for bullets). It does not touch look, palette, width or credit, so it is above baseline but not exhaustive.

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?

Opens with a specific verb and artifact: "Generate a slide-deck-quality chevron process diagram: 2–7 phases drawn as arrow-shaped chevrons left to right." It enumerates the exact visual features (timing line, bullets, highlight) so the agent can distinguish this from create_cycle, create_timeline, or create_org_chart without opening a 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 criteria ("our approach" slide, delivery phases, sales or onboarding process, short linear sequence where ORDER matters) and explicit negative routing with named sibling categories: timeline for exact dates/overlapping durations, cycle diagram for loops, org chart or mind map for branching. Nothing is left to inference.

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