Skip to main content
Glama

Two Minute Toolkit

Two Minute Stop Start Continue

create_stop_start_continue
Read-onlyIdempotent

Generate a slide-deck-quality Stop Start Continue chart: three equal columns, Stop (red, a stop-sign marker), Start (emerald, a play marker) and Continue (sky, a circular-arrow marker), each a softly tinted panel with up to 8 bullets, plus an optional subject ("Sprint 14 retro") and an optional conclusion band for the agreed actions. Set order: "start-stop-continue" when the user puts Start first; rename columns with labels (e.g. { "continue": "Keep doing" }). Choose it for sprint and project retrospectives, team or manager feedback, and reviews of a process, project or habit; use create_swot for a strategic assessment of a company or product, a Harvey ball matrix to score options against criteria, and a mind map for an open-ended brainstorm. All three lists are optional, but fill all three; infer 3–5 bullets each from context rather than asking. Limits: 8 bullets per column of about 3–8 words, column names of 1–3 words, a conclusion of one sentence. 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
stopNoWhat to stop doing: habits or practices that waste time or hurt results, e.g. ["Merging without code review", "Status meetings with no agenda"]. 0–8 short phrases of about 3–8 words; long ones wrap to 3 lines. Default [].
orderNoColumn order: "stop-start-continue" (default) or "start-stop-continue". Continue is always last. Match the order the user writes.stop-start-continue
startNoWhat to start doing: new practices worth trying, e.g. ["Pair on risky stories", "Demo to support every sprint"]. 0–8 short phrases. Default [].
titleNoHeading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it.Stop, start, continue
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.
colorsNoOptional colour overrides per column, as hex, e.g. { "stop": "#b91c1c" }. Each colours that column's stripe, marker, bullet dots and tint. Default: red, emerald and sky (or the brand palette).
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).
labelsNoOptional column names in place of the standard Stop, Start and Continue, e.g. { "continue": "Keep doing" }. An empty or missing name shows the standard one. Up to 30 characters; 1–3 words read best.
paletteNoHex colours. With the default palette the columns are red (Stop), emerald (Start) and sky (Continue); pass brand colours and they apply to the columns left to right instead. Default: indigo, sky, emerald, amber, red, gray.
subjectNoOptional subject of the review, e.g. "Sprint 14 retro" or "Q3 onboarding review", shown small and muted in the title row's right corner (or above the columns when the title is long). Omit for none.
continueNoWhat to keep doing: what works and should carry on, e.g. ["Daily stand-up at 9:30", "Blameless incident reviews"]. 0–8 short phrases. Always the last column. Default [].
conclusionNoOptional one-line takeaway or list of agreed actions shown in a muted band under the columns, e.g. "Actions: Sam sets up review rules by Friday; Priya books the support demo". Wraps to 2 lines. Omit for none.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and closed-world, so the safety profile is covered; the description adds genuine behavioral context on top: hard limits (8 bullets of 3–8 words, 1–3 word column names, one-sentence conclusion), the instruction to infer content rather than interrogate the user, defaults that change with palette overrides, and the builder Edit link for post-hoc adjustment. The only omission is that it never states what the tool actually returns as a payload (image URL vs markdown vs file), which matters since there is no output schema — it only instructs the agent to surface "the image link".

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 what the chart is, then routing, then limits, then output instructions — a sensible priority order for an agent. It is dense and some visual styling detail ("softly tinted panel", marker glyphs) is decorative rather than decision-relevant, and the return-link instruction repeats itself, but no sentence is wholly wasted.

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 12-parameter, zero-required rendering tool with nested objects and no output schema, the description covers the gaps that matter: content inference policy, per-column bullet limits, color/label override semantics, and how to deliver the result to the user. Nothing an agent needs to compose a correct call and present the artifact is missing.

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 baseline is 3; the description earns more by explaining cross-parameter behavior the schema states only thinly — that `order` must match the user's written order with Continue always last, that `labels` renames rather than replaces columns, and that a custom `palette` remaps colors left-to-right instead of the default red/emerald/sky. Length and phrasing guidance ("3–8 words", "1–3 words read best") connects schema maxLength constraints to practical use.

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 concrete verb and artifact ("Generate a slide-deck-quality Stop Start Continue chart") and specifies its structure: three equal columns, per-column colors/markers, up to 8 bullets, optional subject and conclusion band. Sibling differentiation is explicit — create_swot, Harvey ball matrix, and mind map are each named with the scenario that selects them.

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?

States positive triggers precisely ("sprint and project retrospectives, team or manager feedback, and reviews of a process, project or habit") and then gives explicit exclusions with alternatives: create_swot for strategic company/product assessment, Harvey ball matrix for scoring options, mind map for open-ended brainstorm. An agent can route between four related chart tools without opening another schema.

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