Skip to main content
Glama

Two Minute Toolkit

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.

Input Schema

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

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, and closed-world behavior, but the description adds important operational context: infer missing details instead of asking, users can adjust via the Edit link, and the image link must always be given because inline chat images may not save. These are non-obvious behaviors not captured in annotations or schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Despite being detailed, it is front-loaded with the core purpose and then organized into when-to-use, alternatives, limits, behavioral guidance, and output-link handling. Every sentence serves a clear selection or invocation purpose.

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?

There is no output schema, but the description explains the generated chart, its limits, the Edit link, and the essential image-link return behavior. Combined with rich parameter descriptions, an agent has everything needed to call and use the tool correctly.

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 the schema already documents all seven parameters thoroughly. The description reinforces phase count, bullet limits, timing, and the highlight option, but does not add substantial parameter semantics beyond what is already in the schema.

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 uses a specific verb and resource ('Generate a slide-deck-quality chevron process diagram') and explicitly distinguishes the tool from timeline, cycle, org chart, and mind map alternatives. An agent can identify the exact chart type this tool creates 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?

It gives concrete use cases ('our approach', delivery phases, sales/onboarding process, short linear sequences where order matters) and explicit alternatives for adjacent situations: timeline for dates/overlaps, cycle for loops, org chart/mind map for branching. Limits and preferred phrasing are also stated.

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