Skip to main content
Glama

Two Minute Org Chart

create_org_chart
Read-onlyIdempotent

Generate a slide-deck-quality org chart: a tree of people cards (name, role, initials circle) joined by elbow connectors, top-down or left-right. Colour is automatic: each team under the root (each of the root's direct reports and everyone below them) gets its own palette colour; set color on a card only to override that. Choose it whenever the point is WHO reports to or works with whom: reporting lines, project or engagement teams, governance and steering structures. Use a mind map instead for ideas or topics radiating from a central theme, and a hub and spoke for one centre with peers around it. Nest people in children under root; more than 4 reports with no reports of their own are stacked in a column automatically. Limits: 60 people, 5 levels. 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": "Dana Lee",
        "role": "Engagement lead",
        "children": [
          {
            "name": "Sam Ortiz",
            "role": "Tech lead",
            "children": [
              {
                "name": "Two engineers",
                "role": "Build"
              }
            ]
          },
          {
            "name": "Priya Shah",
            "role": "Design lead"
          },
          {
            "name": "Alex Chen",
            "role": "Product owner"
          }
        ]
      },
      "title": "Project team"
    },
    "name": "create_org_chart"
  }
}

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 top of the tree (the lead, manager or sponsor) with everyone else nested under it in `children`. Limits: 60 people and 5 levels in total (the root is level 1); extra people are dropped with a warning, deepest levels and last-listed people first.
titleNoHeading shown top-left of the chart at 22px bold. Every chart has one title row; an empty string hides it.Team Structure
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).
layoutNo"top-down" (default): the root at the top, reports in rows below. "left-right": the root on the left, reports in columns to the right, which suits deep or very wide trees.top-down
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.
showInitialsNoShow an initials circle on each card, in the card's team colour. Default true. There are no photos.

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

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds genuine behavior: automatic per-team palette assignment, automatic column stacking for more than 4 leaf reports, hard limits of 60 people and 5 levels with dropped nodes warned, and an instruction to infer missing details rather than ask. However, it omits the return payload shape beyond telling the agent to share the image link, so it is strong but not complete on what comes back.

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?

One dense paragraph, front-loaded with what the chart looks like before moving to selection guidance, limits and output handling. All sentences are load-bearing, but the block is long and the limits and output-link advice would scan better as separate sentences or lines.

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

Completeness3/5

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

With 8 parameters, deep nesting and no output schema, the description covers limits, auto-layout behavior and the image-link delivery convention well. It does not describe error or truncation feedback beyond a warning, nor what the returned object contains, which leaves a gap for a tool with no output schema.

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 earns more by explaining the color override rule ('set `color` on a card only to override' the automatic per-team palette) and how nesting in `children` under `root` drives the tree structure. The width and look parameters are left to the schema, which already documents them well.

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 artifact ('Generate a slide-deck-quality org chart') plus the visual composition (people cards with name, role, initials, elbow connectors, top-down or left-right). It explicitly differentiates from siblings by naming mind map and hub-and-spoke as alternatives.

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 whenever the point is WHO reports to or works with whom') with concrete scenarios (reporting lines, project teams, governance structures) and names the two sibling tools to use instead for adjacent intents, with the condition that selects each.

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