Two Minute Toolkit

Two Minute Pyramid / Funnel

create_pyramid

Read-onlyIdempotent

Generate a slide-deck-quality pyramid or funnel: 2–8 stacked layers in even steps, narrow at the top in pyramid mode (a hierarchy of needs, a strategy pyramid, foundations to vision) or wide at the top in funnel mode (sales, marketing or hiring funnels). Each layer has a name and an optional detail line beside it. Choose it when items stack in a ranked order or narrow down stage by stage; use a process diagram for a sequence of phases of equal weight, a cycle for a loop, a hub and spoke for parts around a centre, and a timeline when dates matter. Limits: 2–8 layers; keep names to one to four words and details to one short 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

Name	Required	Description	Default
`mode`	No	"pyramid" (default) narrows toward the top layer, for hierarchies and foundations-to-vision stacks. "funnel" is widest at the top and narrows down, for sales, marketing and hiring stages. Layers are always listed top to bottom.	pyramid
`title`	No	Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it.	Pyramid
`width`	No	Chart width in pixels (640–2400). Omit it (recommended) and the chart sizes itself to its content with comfortable margins, between 880 and 1280px wide. PNG output renders at 2x.
`credit`	No	Shows 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).
`layers`	Yes	The layers, top to bottom (2–8; extra layers are dropped with a warning). In a pyramid the first layer is the narrow tip; in a funnel it is the wide first stage. Names sit inside the shape when they fit, otherwise beside it with a leader line.
`palette`	No	Hex 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.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations only cover the read-only/idempotent profile, and the description adds real behavioural context beyond that: the 2–8 layer cap with extras 'dropped with a warning', label-fit behaviour (names inside the shape or beside it with a leader line), auto-sizing, and the critical fact that inline chat images usually cannot be saved so the link must be given. That is exactly the non-obvious behaviour an agent needs.

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, then usage routing, then limits, then delivery instruction — a sensible priority order. It runs long and repeats the 2–8 layer limit that the schema already enforces via minItems/maxItems, which costs it a point.

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?

No output schema exists, and the description compensates fully by explaining what the agent gets back (an image plus an Edit link) and how to hand it to the user. Nothing an agent needs to call this correctly or report the result is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/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, but the description adds authoring guidance the schema lacks — names to one to four words, details to one short sentence, layers listed top-to-bottom with opposite meaning in each mode. It reinforces the mode/ordering semantics that are the most error-prone part of the call.

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?

States a specific verb and resource ('Generate a slide-deck-quality pyramid or funnel') and immediately defines both modes with concrete use cases (hierarchy of needs, sales funnel). An agent can distinguish this from create_process, create_cycle, create_hub_spoke and create_timeline without opening any 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?

Explicit selection criteria: 'Choose it when items stack in a ranked order or narrow down stage by stage', followed by named alternatives and the condition that selects each (process = equal-weight phases, cycle = loop, hub and spoke = parts around a centre, timeline = dates matter). It also states operational policy — infer missing details rather than asking, and always surface the image link.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Two Minute Toolkit tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?