Skip to main content
Glama

Get a chart's props + example

get_microchart

Get full wiring details for a chart by slug: import paths, props, data shape, best practices, runnable example, and sample JSON for rendering.

Instructions

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 sample — the example as JSON props you can pass straight to render_microchart.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesChart slug, e.g. "sparkline".

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
slugYes
propsYes
sampleNoReady-to-render props — pass straight to render_microchart.
statusYes
bestForYes
exampleYes
gotchasNoBehavior no prop description carries: documented caps, inputs the component derives, how format meets the chart's own sign or unit, and sizing knobs that are not width/height. Read before writing props.
taglineYes
avoidForYes
encodingYes
maxWidthNoAuthored maximum width prop, viewBox units. Past it the geometry stops scaling and the extra box is whitespace — scale with CSS instead. Absent on charts sized by cell, by content, or by CSS.
dataShapeYes
maxHeightNoAuthored maximum height prop, viewBox units.
sharedPropsYes
staticImportYes
interactiveImportNo
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It lists exactly what is returned (import paths, props, data shape, best/avoid guidance, copy-runnable example, and sample), providing good transparency for a read-only retrieval tool. It does not mention side effects or errors, but for a get tool this is adequate.

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?

The description is a single comprehensive sentence that front-loads the key action and enumerates contents efficiently. It is slightly run-on but not overly verbose, and every part adds value.

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 only one parameter and an output schema present, the description thoroughly covers what the tool provides and even connects to render_microchart via the sample field. There are no significant gaps for this simple tool.

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% with 'slug' described as 'Chart slug, e.g. "sparkline"'. The description only restates 'by slug' without adding extra parameter semantics, so it does not improve upon the schema. Baseline 3 is appropriate.

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 states a specific action: 'Full wiring detail for one chart by slug' and enumerates the exact contents (import paths, props, data shape, guidance, example). It distinguishes from siblings by mentioning the sample can be passed to render_microchart, and the title clarifies it's about props and example.

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?

Clear context: use this tool to get comprehensive details for a known chart slug, and the 'sample' output can be fed to render_microchart. It does not explicitly exclude when to use find_microchart, but the sibling names imply differentiation, so there is clear context without explicit exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ganapativs/microcharts'

If you have feedback or need assistance with the MCP directory API, please join our Discord server