Skip to main content
Glama

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.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "mode": "funnel",
      "title": "Sales funnel",
      "layers": [
        {
          "name": "Leads",
          "detail": "Everyone who showed interest"
        },
        {
          "name": "Qualified",
          "detail": "Need and budget confirmed"
        },
        {
          "name": "Proposal"
        },
        {
          "name": "Won"
        }
      ]
    },
    "name": "create_pyramid"
  }
}

Input Schema

NameRequiredDescriptionDefault
lookNoDrawing style, the same in every tool. "regular": clean lines and Inter (the default). "bold": heavier, slightly larger type and thicker lines, for slides read from a distance. "sketch": hand-drawn, with a handwriting font and pen lines that wobble a little, for early ideas and workshops. Use the one the user asks for; otherwise leave it out.regular
modeNo"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
titleNoHeading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it.Pyramid
widthNoChart 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.
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).
layersYesThe 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.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / look
      Added value: +{
      +  "default": "regular",
      +  "description": "Drawing style, the same in every tool. \"regular\": clean lines and Inter (the default). \"bold\": heavier, slightly larger type and thicker lines, for slides read from a distance. \"sketch\": hand-drawn, with a handwriting font and pen lines that wobble a little, for early ideas and workshops. Use the one the user asks for; otherwise leave it out.",
      +  "enum": [
      +    "regular",
      +    "bold",
      +    "sketch"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint, idempotentHint and openWorldHint=false, so the description carries the operational burden and does: hard limits (2–8 layers, one-to-four-word names, one short sentence of detail), what happens to excess layers (dropped with a warning), and the return channel (an image link that re-renders the chart on demand because inline chat images usually cannot be saved). That last point is genuinely non-obvious behaviour an agent would otherwise get wrong.

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 the core verb and the pyramid/funnel split, then routing rules, then limits, then the output-link instruction — a sensible priority order with no filler. Slight redundancy remains: "Each layer has a name and an optional detail line beside it" restates what the layers schema already documents.

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 fills that gap by describing the artifact returned (a chart rendered at a link, editable via the builder's Edit link) and why the link matters over the inline image. For a 7-parameter generator with a 100%-documented schema, nothing an agent needs in order to call 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 the baseline is 3; the description earns a point by explaining the ordering semantics that the schema only hints at — layers are always listed top to bottom, so the first layer is the narrow tip in pyramid mode but the wide first stage in funnel mode, and names fall outside the shape with a leader line when they don't fit. Minor friction: the description says "2–8 layers" while the schema allows minItems 1, though the schema's own text reconciles this as dropped-with-warning.

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 pins down the two variants: 2–8 stacked layers, narrow-at-top pyramid vs wide-at-top funnel, with concrete example use cases for each. An agent can distinguish this from create_process or create_org_chart 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?

Gives an explicit selection rule ("Choose it when items stack in a ranked order or narrow down stage by stage") and names four alternative tools with the exact condition that selects each — process for equal-weight phases, cycle for loops, hub and spoke for parts around a centre, timeline when dates matter. It also handles the fallback behaviour (infer missing details rather than asking) and the post-call obligation (always surface the image link, with the reason).

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