microcharts
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_microchartA | Rank microcharts chart types against a plain-language question about data ("is it trending?", "error budget", "part to whole"). Returns candidates with the reason each matched. Start here when you know the question, not the chart. |
| get_microchartA | Full wiring detail for one chart by slug: import paths, its props plus the shared props, data shape, best/avoid guidance, a copy-runnable example, and |
| render_microchartA | Render a chart to a finished, self-contained SVG (styles embedded) plus its generated alt text — for surfaces that can't run React. Pass the series as |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| catalog | Every chart type with metadata, props, and the library version stamp. |
| agent-setup | The canonical prompt for wiring microcharts into a codebase. |
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: find discovers chart types, get retrieves implementation details, and render produces the final SVG. There is no meaningful overlap between querying, inspecting, and rendering.
All tool names follow the same verb_noun pattern: find_microchart, get_microchart, render_microchart. The naming is predictable and makes the workflow easy to infer.
Three tools is well-scoped for the server's purpose: discover a chart, understand its wiring, and render it. Each tool is necessary and the set is tight without unnecessary duplication.
The tools form a complete workflow: find_microchart returns candidates to identify the right chart, get_microchart provides the data shape and sample needed to render, and render_microchart produces the final SVG output. There are no dead ends or obvious missing operations.