Skip to main content
Glama

Two Minute Toolkit

Two Minute Harvey Ball Matrix

create_harvey_matrix
Read-onlyIdempotent

Generate a slide-deck-quality Harvey ball matrix: options as rows scored against criteria as columns, every cell drawn in one style (Harvey balls 0–4 from empty to full, ticks 0/1, or 0–5 dots), with an optional highlighted 'Recommended' row, an optional notes column (appears when any row has notes) and a legend. Choose it to compare vendors, tools, plans or features side by side; use a timeline when the point is WHEN work happens, a process for ordered steps, a pyramid/funnel for a hierarchy or narrowing stages, and a hub and spoke, mind map or org chart for relationships. Limits: 2–12 rows, 1–8 criteria, row names up to 40 characters; scores outside the style's range are clamped and null leaves a cell blank. 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
rowsYesThe options being compared, top to bottom (2–12). Each has a name and one score per criterion, in the same order as `criteria`.
notesNoShow the Notes column on the right. true shows it even when no row has a note yet; false hides it (any row notes are kept but not drawn). When omitted, the column appears automatically as soon as any row has a note, so you can simply set rows[].notes.
styleNoCell style for the whole grid: "harvey" (Harvey balls, scores 0–4 from empty to full), "check" (a tick for 1, nothing for 0) or "dots" (0–5 filled dots out of five). Default "harvey".harvey
titleNoHeading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it.Comparison
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).
legendNoShow a one-line legend under the grid explaining the scale. Default true.
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.
criteriaYesColumn headings, left to right: what each option is scored on, e.g. ["Cost", "Ease of use", "Integrations"]. 1–8 criteria, up to 40 characters each; long names wrap to two lines.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/idempotent annotations, it discloses hard limits (2–12 rows, 1–8 criteria, 40-char names), out-of-range handling (scores clamped, null leaves blank), and the conditional Notes column. It also explains the delivery behavior: the image link must always be given because inline images can't be saved, and an Edit link lets the user adjust.

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 purpose, followed by routing, limits, and output instructions; every sentence carries some action-relevant content. It's dense for a single paragraph, and the limits clause partially duplicates schema constraints, but nothing is filler.

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 9-parameter generative tool with no output schema, it covers structure, defaults-by-omission, edge cases (clamping, blank cells), and what the caller must return to the user. Nothing an agent needs to invoke it correctly 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 most parameter meaning is already structured; the description's limits restate schema min/max values. It does add cross-field semantics — score ranges tied to the chosen style, clamping, and blank cells from null — which helps an agent populate rows[] correctly rather than reading each property doc.

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+artifact ("Generate a slide-deck-quality Harvey ball matrix") and immediately defines the row/column structure and cell styles. It explicitly names the sibling types it is not (timeline, process, pyramid/funnel, hub and spoke, mind map, org chart), so an agent can route correctly without opening other 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 a positive selection rule ("compare vendors, tools, plans or features side by side") plus explicit when-to-use-an-alternative rules mapped to each competing sibling. It also advises inferring missing details rather than asking, which removes a common agent stall.

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