Skip to main content
Glama

Chart chooser

chart_chooser
Read-only

Pick a chart type from the question being asked and the shape of the data. Pass question (compare, trend, distribution, part-to-whole, relationship, ranking, geography) and any of: categories (number of groups or items), points (observations or time steps), series (number of series), thirdVariable (relationship questions: a third measure to encode), hierarchy (parts nest inside parts), overTime (the question is across time), audience (general or analyst). Returns ranked chart types, each with a reason tied to your numbers, avoid (chart types that mislead for this question) and notes. Draws on the practice described by Stephen Few (Show Me the Numbers) and Alberto Cairo (The Functional Art); the rankings are our own judgment, not a formula. Pure computation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "question": "<question>"
    },
    "name": "chart_chooser"
  }
}

Input Schema

NameRequiredDescriptionDefault
pointsNoNumber of observations or time points.
seriesNoNumber of series.
audienceNoWho reads it.
overTimeNoThe question spans time.
questionYesWhat the reader should be able to answer.
hierarchyNoParts nest inside parts (part-to-whole).
categoriesNoNumber of categories or items.
thirdVariableNoA third measure is available (relationship).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already mark it read-only and non-destructive, and the description adds that it is pure computation, that rankings are judgment rather than formula, and what the return fields mean. This is substantial extra context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded purpose followed by tight parameter detail and a brief note on provenance. No sentence is wasted.

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, so the description provides the return shape (ranked, avoid, notes) and explains the tool's judgment-based nature. Complete enough for an agent to call it correctly.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents every parameter. The description repeats the parameter meanings in prose but adds little beyond the schema.

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 outcome: pick a chart type from the question and data shape. It clearly distinguishes chart selection from sibling tools like chart_lint and chart_colour_check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explains exactly what to pass, including the question types and optional data-shape parameters. It gives clear usage context but does not name alternatives or when not to use this tool.

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