Skip to main content
Glama

Two Minute Toolkit

Two Minute 2×2 Matrix

create_quadrant_matrix
Read-onlyIdempotent

Generate a slide-deck-quality 2×2 matrix, the classic consulting quadrant slide: two labelled axes (name plus low and high ends, rotated on the left) and four quadrants tinted in one accent colour. Two modes: "plot" places items as dots at x and y on 0–10 scales (or bubbles sized by size), with every label placed automatically so none overlap and quadrant names faint in the corners; "list" gives each quadrant a bold name and up to 6 bullets. Choose it to prioritise or position things on two dimensions: tasks, initiatives, features, products, brands, stakeholders or risks. Pick the preset that matches the request and let it supply the standard axes, quadrant names and mode: impactEffort for impact vs effort, quick wins or an action priority matrix; eisenhower for urgent vs important or a to-do list; bcg for a growth-share or product portfolio matrix (give revenue as size); ansoff for growth strategy (products × markets); powerInterest for a stakeholder map; perceptual for a perceptual or competitive positioning map (rename the axes to the user's attributes); riskLikelihood for a likelihood vs impact risk grid; none for any other 2×2 (name the axes and quadrants yourself; an omitted preset means none). Quadrants are keyed by position: topLeft, topRight, bottomLeft, bottomRight; with normal axes topRight is high x, high y. Use a Harvey ball matrix to score options against several criteria, create_five_forces for one industry's competitive forces, and create_swot for strengths, weaknesses, opportunities and threats. Infer realistic positions from context rather than asking. Limits: 30 items, names up to 40 characters (1–4 words read best), 6 bullets per quadrant. 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
modeNo"list": four tinted quadrants, each with its name and bullets. "plot": items drawn as dots or bubbles at their x and y, with quadrant names faint in the corners. Omit to use the preset's mode (list for eisenhower and ansoff, plot for the rest).
itemsNoPlot mode only (kept but not drawn in list mode): 0–30 items, each a dot at its x and y on 0–10 scales, with its name beside it, e.g. { "name": "Self-serve onboarding", "x": 2.5, "y": 8 }. Labels are placed automatically so they never overlap. Give `size` to draw bubbles.
titleNoHeading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it.2×2 matrix
widthNoChart width in pixels (640–2400, default 1280, which suits a 16:9 slide). PNG output renders at 2x. Height follows from the width (plot mode) or the bullets (list mode).
xAxisNoThe horizontal axis along the bottom, e.g. { "label": "Effort", "low": "Low", "high": "High" }. Each field you omit comes from the preset; an empty string hides that text.
yAxisNoThe vertical axis up the left side, with rotated texts, e.g. { "label": "Impact", "low": "Low", "high": "High" }. Each field you omit comes from the preset; an empty string hides that text.
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).
presetNoSet it: the standard matrix to start from, or "none" (the default when omitted). Its axis labels, quadrant names and mode fill in anything the payload leaves out (your own values always win). eisenhower: urgency (urgent on the LEFT) × importance; Do first, Schedule, Delegate, Eliminate; list. impactEffort: effort × impact; Quick wins (top left), Major projects, Fill-ins, Thankless tasks; plot. bcg: relative market share (high on the LEFT) × market growth; Stars, Question marks, Cash cows, Dogs; plot. ansoff: products (existing, new) across × markets (existing at the TOP, new below); Market penetration, Product development, Market development, Diversification; list. powerInterest: interest × power; Keep satisfied, Manage closely, Monitor, Keep informed; plot. perceptual: price × quality; High value, Premium, Economy, Overpriced; plot. riskLikelihood: likelihood × impact; Plan contingency, Act now, Accept, Monitor; plot. none: plain Low/High axes and no quadrant names, plot (name the axes and quadrants yourself).none
paletteNoHex colours. The whole matrix uses the FIRST palette colour as its one accent, tinted in four strengths across the quadrants, so a brand colour as the first entry recolours the chart. Default: indigo, sky, emerald, amber, red, gray.
showGridNoPlot mode: light gridlines at every whole unit (1–9) behind the items. Default false (the midlines only).
quadrantsNoThe four quadrants by POSITION on the slide (after any axis reversal): topLeft, topRight, bottomLeft, bottomRight. With both axes in their normal direction, topRight is high x and high y, bottomLeft low x and low y. Each is { "name", "bullets", "color" }, all optional; a missing name comes from the preset. E.g. { "topLeft": { "name": "Quick wins", "bullets": ["Fix checkout bug"] } }.

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?

The annotations declare a safe, idempotent read with no external world access, and the description is consistent with that while adding substantial operational context: hard limits (30 items, 40-character names, 6 bullets per quadrant), automatic non-overlapping label placement, tinting from the first palette colour, and an always-emit-the-image-link instruction with the reason (inline chat images cannot be saved). It also points the user to the Edit link, which the agent could not infer from the annotations.

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

Conciseness3/5

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

The purpose is front-loaded and the closing image-link instruction is well placed, but the middle is a dense run-on block that re-enumerates preset axis and quadrant details already fully specified in the preset enum. Those sentences do not earn their place twice and make the definition harder to scan than it needs to be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly covers output delivery (always return the image link, why inline images fail, pasteability into slides or Markdown) and the edit path. For an 11-parameter, nested-schema tool this is nearly complete; only the exact response payload shape is left implicit.

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 schema already carries the per-field detail; the description still adds routing value the schema does not, such as 'give revenue as size' for BCG bubbles and 'rename the axes to your attributes' for perceptual maps, plus 'an omitted preset means none'. It does not add much on width, palette, or reverse-flag behaviour beyond the schema, so it sits above the 3 baseline but not at the top.

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 opening sentence names the concrete artifact ('slide-deck-quality 2×2 matrix, the classic consulting quadrant slide') and immediately distinguishes the two output shapes: items plotted as dots versus bullets per quadrant. It stays clearly distinct from siblings like create_harvey_matrix and create_swot, which are named later.

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?

The description explicitly states when to choose it ('prioritise or position things on two dimensions: tasks, initiatives, features, products, brands, stakeholders or risks'), gives a preset-to-use-case mapping (impactEffort for quick wins, bcg for growth-share, eisenhower for to-do list), and names three alternatives plus the condition that selects them (Harvey balls for scoring against criteria, create_five_forces, create_swot). This is about as complete as routing guidance gets.

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