Skip to main content
Glama
blueprint-chart

blueprint-chart/mcp

render

Idempotent

Convert .bpc chart source into SVG, PNG, or HTML. PNG returns as an inline image for immediate visual review, with optional file-saving to disk.

Instructions

Render a .bpc source to SVG (default), PNG, or HTML. With format:"png" the chart comes back as an inline IMAGE you and the user can both see — render, look at the result, fix issues, re-render. Always returns structured frame metadata. When MCP_PUBLIC_URL is set the response includes stateless urls ({png,svg,bpc}). Set modelVisible:false to display the image to the user without spending model image tokens. Pass save:<path> to write the output into MCP_FS_WRITE_DIR instead of returning it inline. Width/height are capped at 1600; PNGs are rasterized at 2× for retina sharpness.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
saveNoOptional output path, always resolved inside MCP_FS_WRITE_DIR (relative paths are joined to it; absolute paths are re-anchored under it). When set, the output is written to disk and omitted from the response. Requires MCP_FS_WRITE_DIR.
sceneNoZero-based scene index to render, for charts that define scenes. Omit for the base chart (scene 0).
widthNoOutput width in pixels (max 1600). PNGs are rasterized at 2x for retina sharpness.
formatNoOutput format. "svg" (default) and "html" return text; "png" returns an inline image you and the user can both see.svg
heightNoOutput height in pixels (max 1600).
sourceYesThe .bpc chart source to render.
modelVisibleNoWhen false, the inline PNG is shown to the user but not sent to the model (saves image tokens on bulk renders).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlsNoStateless hosted render URLs (only when MCP_PUBLIC_URL is set).
frameYesFrame metadata extracted from the chart.
savedToNoAbsolute path the output was written to, when `save` was used.
mimeTypeYesMIME type of the rendered output.
urlsOmittedNoSet when URLs were omitted because the source exceeded the URL cap.
Behavior5/5

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

The description discloses many behavioral traits beyond the annotations: inline image behavior for PNG, structured frame metadata, stateless URLs under MCP_PUBLIC_URL, save path behavior with MCP_FS_WRITE_DIR, width/height caps, and 2× retina rasterization. It complements the idempotentHint and non-destructive annotations without contradiction.

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?

The description is dense yet efficient, front-loading the core purpose in the first sentence and then delivering actionable details without fluff. Every sentence adds value, covering formats, image visibility, metadata, URLs, saving, and size caps.

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?

Given the rich input schema, annotations, and output schema, the description covers all important behavioral aspects: output formats, inline image behavior, save semantics, model visibility, size caps, and environment-dependent URLs. It is sufficiently complete for an agent to use the tool correctly.

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 baseline is 3. The description adds extra meaning for format (inline image vs text), save (writes to disk and omits from response), and modelVisible (toggles image token consumption), which goes beyond the schema's per-parameter descriptions.

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 clearly states the tool's core function with a specific verb and resource: 'Render a .bpc source to SVG (default), PNG, or HTML.' It also differentiates from siblings by focusing on rendering output, while siblings like validate_dsl and inspect_dsl handle validation/analysis.

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?

The description provides clear context on how to use the tool: iterative render-fix cycles, saving to disk with save:<path>, controlling model visibility with modelVisible:false, and explaining format choices. However, it does not explicitly mention alternatives or when not to use this tool, so it stops short of a 5.

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/blueprint-chart/mcp'

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