Skip to main content
Glama
Sign In
ChartQuery MCP Server

ChartQuery MCP Server

by chartquery
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Label Render

label_render
Read-only

Render a previously saved label by ID in SVG or PNG, and optionally filter returned fields or override the output format.

Instructions

Label Render. Render a previously saved label by ID. Public, no API key required. Supports ?format= override.

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": {
      "id": "<id>"
    },
    "name": "label_render"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
fieldsNoComma-separated list of fields to keep in the response, with dot notation for nested fields (e.g. name,location.city). Does not change the credit cost.
formatNoOverride output format. Allowed values: svg, png. Default: "svg".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuinely useful access context ("Public, no API key required") not present in the annotations, but says nothing about error behavior for unknown IDs, output size, or rate limits.

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?

Three short front-loaded sentences with no filler; the core verb and precondition come first. The trailing "?format= override" uses URL query syntax rather than tool-parameter phrasing, which is slightly awkward but not wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 3-parameter render tool with no output schema, the description omits what actually comes back (raw image bytes, URL, or an inline SVG string) and whether rendering consumes credits — a notable gap given the fields parameter mentions credit cost. The essentials for invoking it are present, but the return contract is left to inference.

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 description coverage is 67%, and the id parameter carries an empty description while the description only echoes "by ID" — it never says what form the ID takes or where to obtain it. The fields and format parameters are already fully explained by the schema, so the description adds almost nothing beyond baseline.

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?

Uses a specific verb ("Render") with a clear resource and precondition ("a previously saved label by ID"), which separates it from siblings that compile or validate label markup. It stops short of naming which sibling to use instead, but the purpose is unambiguous.

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?

"Previously saved label" implies the prerequisite state (the label must already exist and have an ID), but there is no explicit when/when-not guidance or reference to label_compile or label_view as alternatives. An agent must infer the boundary from context.

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