Skip to main content
Glama

UrlChart

Generate a chart image

generate_chart_image

Render a PNG chart through UrlChart and return the image plus its hosted URL. Accepts Google Image Charts / legacy parameters as an object ({"cht":"bvg","chs":"400x200","chd":"t:10,40,80"}) or a full legacy chart URL (Google, Image-Charts, QuickChart or urlchart.com). Without an api_key (or an Authorization: Bearer header on this MCP connection) the render is the FREE tier: a canvas of at most 1000 px per side / 1 MP, 60 requests/minute and 1,000 unique renders/month per IP. A request above that canvas is scaled down and reported in X-UrlChart-Meta, never failed. A paid api_key keeps the full 9 MP canvas (3000 px per side) and applies the paid limits. Parameters that are unknown or not implemented never fail the render; they degrade and are reported in X-UrlChart-Meta. chof=jpg|webp|pdf requests another output format; a PDF result is returned as a hosted URL (not an image block). The hosted URL in the text result is the same chart without any credential, so embedding it publicly serves the FREE (capped-canvas) variant unless a key or signed URL is added.

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": {
      "params": "<params>"
    },
    "name": "generate_chart_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
paramsYesLegacy chart parameters. Either an object of parameter name -> value (cht, chs, chd, chds, chl, chdl, chdlp, chxt, chxl, chxr, chxs, chxp, chxtc, chco, chtt, chts, chma, chg, chf, chbh, chls, chm (and chld/choe for cht=qr)), or a full chart URL / query string. Values may be strings or numbers.
api_keyNoOptional UrlChart API key (uc_live_… / uc_test_…). Omit to use the free tier. Alternatively send `Authorization: Bearer <key>` on the MCP request itself.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so thoroughly: free-tier ceilings (1000 px/side, 1 MP, 60 rpm, 1,000 renders/month per IP), paid tier at 9 MP/3000 px, oversized canvases scaled down rather than failed, unknown parameters degrading with reporting in X-UrlChart-Meta, and PDF returned as a URL instead of an image block. It also warns that the hosted URL is uncredentialed, so public embedding silently serves the capped free variant.

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?

Front-loaded with the core action, then tier, then format caveats, then the credential warning—a sensible order. It is dense and several sentences pack multiple clauses, but nearly every clause carries operational information; only the legacy-parameter enumeration overlaps with the schema.

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?

For a two-parameter tool with no output schema and no annotations, the description covers the return shape (image block plus hosted URL, or URL only for PDF), tier behavior, degradation on bad input, and the credential caveat on public URLs. Nothing an agent needs in order to call this correctly appears to be missing.

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, and the description earns an extra point by adding meaning the schema doesn't: the consequence of omitting api_key (free-tier caps), the header-based credential alternative, chof output-format semantics, and the fact that PDF output changes the return shape. The long list of legacy parameter names is largely duplicative of the schema's enumeration.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Render a PNG chart through UrlChart and return the image plus its hosted URL.' The phrase 'return the image' implicitly separates it from a URL-builder sibling, but no sibling (build_chart_url, check_legacy_chart_url) is named or contrasted, so an agent must infer the boundary.

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

Usage Guidelines3/5

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

Usage context is implied rather than stated: reach for this when an actual rendered image block is needed (versus a URL), and use chof=jpg|webp|pdf for other formats. There is no explicit when-not guidance and no named alternative for situations where a URL alone suffices.

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.