Skip to main content
Glama

Two Minute Issue Tree

create_issue_tree
Read-onlyIdempotent

Generate a slide-deck-quality issue tree or driver tree: a key question, problem or top-line metric on the left, broken down left to right into drivers, sub-drivers and hypotheses in clean columns of rounded boxes joined by elbow connectors. Each first-level branch takes its own palette colour. Any box can carry a value ("$12.4m", "+3% YoY") and any parent an operator ("+", "-", "x", "/", drawn as + − × ÷ where its children join) for KPI and value driver trees (Profit = Revenue − Costs; Revenue = Customers × Revenue per customer); levels labels the columns and numbered adds 1, 1.1, 1.1.1. Choose it for consulting issue trees and MECE breakdowns, hypothesis trees, KPI, value and driver trees, root-cause and problem trees: anything where a parent is logically made up of its children. Use a mind map instead for loose brainstorms radiating from a centre with no hierarchy logic or values, and an org chart for people and reporting lines. Limits: 4 levels including the root, up to 6 children per box, 40 boxes; keep labels to a few words. 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": {
      "root": {
        "name": "Operating profit",
        "value": "$4.1m",
        "children": [
          {
            "name": "Revenue",
            "value": "$12.4m",
            "children": [
              {
                "name": "Customers",
                "value": "3,100"
              },
              {
                "name": "Revenue per customer",
                "value": "$4,000"
              }
            ],
            "operator": "x"
          },
          {
            "name": "Costs",
            "value": "$8.3m",
            "children": [
              {
                "name": "Cost of sales",
                "value": "$5.2m"
              },
              {
                "name": "Operating expenses",
                "value": "$3.1m"
              }
            ],
            "operator": "+"
          }
        ],
        "operator": "-"
      },
      "title": "Operating profit driver tree",
      "levels": [
        "Metric",
        "Drivers",
        "Sub-drivers"
      ]
    },
    "name": "create_issue_tree"
  }
}

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
rootYesThe key question, problem or top-line metric on the left (e.g. "Why has profitability declined?" or "Operating profit"), with its drivers nested in `children`. Limits: 4 levels in total including the root, up to 6 children per box and 40 boxes; extras are dropped with a warning, deepest levels and last-listed boxes first.
titleNoHeading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it.Issue tree
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).
levelsNoOptional column labels, left to right, printed in small caps above each level, e.g. ["Key question", "Drivers", "Sub-drivers", "Hypotheses"] (0–4). Omit for none.
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.
numberedNoPrefix every box below the root with its outline number, 1, 1.1, 1.1.1, as consultants number issue trees. Default false.

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.7/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent/closed-world, which is the easy part; the description adds the operational facts an agent actually needs: hard limits (4 levels, 6 children per box, 40 boxes) and what happens on overflow ("extras are dropped with a warning, deepest levels and last-listed boxes first"). It also discloses the delivery constraint — inline chat images can't be saved, so the image link must always be surfaced — and that the user can edit afterwards via the Edit link.

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?

It is one dense block with the purpose and the routing decision reasonably front-loaded, but roughly a third of it is visual styling prose ("clean columns of rounded boxes joined by elbow connectors", palette colouring) that duplicates what the schema already documents and doesn't help tool selection. The high-value material — limits, inference default, image-link instruction — is buried at the tail instead of being promoted.

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 an 8-parameter generative tool with no output schema, the description covers what is produced, the structural limits and overflow behavior, the fallback when details are missing, and how the result should be delivered to the user. Nothing an agent needs in order to call it correctly and hand back the result 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, but the description adds real semantic glue with a worked arithmetic example ("Profit = Revenue − Costs; Revenue = Customers × Revenue per customer") that shows how `operator` and `value` combine across levels — the KPI convention the enum alone doesn't convey. The mentions of `levels` and `numbered` are mostly restatements of the schema and add little.

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+resource ("Generate a slide-deck-quality issue tree or driver tree") and immediately describes the output structure — key question on the left, drivers broken out left to right. It explicitly names the sibling alternatives (mind map, org chart) and the structural test that separates them ("a parent is logically made up of its children"), so an agent can pick it without opening another 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 inclusion list (consulting issue trees, MECE breakdowns, hypothesis trees, KPI/value/driver trees, root-cause trees) and explicit exclusions with the correct alternative for each (mind map for loose brainstorms, org chart for reporting lines). It also states a default behavior for underspecified input: "Infer missing details rather than asking."

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