Skip to main content
Glama

Chart types

chart_types
Read-onlyIdempotent

Lists all chart panel types accepted by plot, including data fields and example calls, to help choose the right chart type and fields before plotting.

Instructions

List every panel type that plot accepts (44 types plus the grammar-of-graphics mark), each with its data fields and a one-line description, followed by a complete example call. Call it before plot when unsure which type fits the data or which fields a type needs. Takes no arguments, reads and writes nothing, and always returns the same text.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chart_types"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, and the description reinforces those without merely repeating them by clarifying that it takes no arguments, reads and writes nothing, and always returns identical text. It also discloses the return contents (per-type data fields, one-line descriptions, and a complete example call), which goes beyond what annotations provide. The only gap is that it doesn't say how large the payload is.

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?

Three tight sentences: the return content comes first, the call-site guidance comes second, and the behavioral caveats come last. No sentence is redundant and none should be cut.

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?

With no output schema, the description carries the burden of explaining the return value, and it does so fully: a list of types with fields and a description, ending in a complete example call. That is enough for an agent to decide whether to call the tool and what to do with the result.

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?

There are zero parameters, so the baseline is 4, and the description explicitly confirms 'takes no arguments,' which is consistent with the empty 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?

The description opens with a specific verb and resource ('List every panel type that plot accepts') and quantifies the scope (44 types plus the `mark` type), which immediately separates it from the sibling plot tool.

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?

It states exactly when to call it — 'before plot when unsure which type fits the data or which fields a type needs' — and implies the inverse (skip it when you already know the type), leaving nothing to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools