Two Minute Issue Tree
create_issue_treeGenerate 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
| Name | Required | Description | Default |
|---|---|---|---|
| look | No | 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. | regular |
| root | Yes | The 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. | |
| title | No | Heading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it. | Issue tree |
| 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). | |
| levels | No | Optional 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. | |
| 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. | |
| numbered | No | Prefix every box below the root with its outline number, 1, 1.1, 1.1.1, as consultants number issue trees. Default false. |