Skip to main content
Glama

UrlChart

Check a legacy chart URL

check_legacy_chart_url

The migration check: analyse a Google Image Charts / Image-Charts / QuickChart URL and report, parameter by parameter, what UrlChart will render, degrade, ignore or not support — plus the equivalent UrlChart URL. Computed from the URL alone: NOTHING is rendered and no request is made to the chart host. Use this before migrating an embed to find out what changes (for example a multi-axis URL that an alternative charts it only on a paid plan).

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": {
      "url": "<url>"
    },
    "name": "check_legacy_chart_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe full legacy chart URL, including https://.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/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 well: it states the result is computed from the URL alone, that NOTHING is rendered, and that no request is made to the chart host — the key side-effect and network disclosure for a safety-conscious agent. It stops short of covering failure behavior for malformed URLs or any rate/limit concerns.

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?

It is a single front-loaded sentence that leads with the core purpose and the no-render guarantee before the migration use case. The em-dash clause and parenthetical example add length but each still carries information, so it is only mildly dense.

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

Completeness4/5

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

No output schema exists, and the description does describe what comes back: a parameter-by-parameter verdict (render/degrade/ignore/unsupported) plus the equivalent UrlChart URL. That is enough for a one-parameter diagnostic tool, with only invalid-input behavior left unspecified.

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?

There is one parameter and the schema description already covers it fully ('The full legacy chart URL, including https://'), so the baseline is 3. The description adds no further meaning about the parameter itself — no accepted URL formats beyond the named providers, no handling of non-legacy URLs.

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 verb and resource: analyse a legacy chart URL (Google Image Charts / Image-Charts / QuickChart) and report per-parameter what UrlChart will render, degrade, ignore or not support, plus an equivalent URL. That scope is clearly distinct from the siblings build_chart_url and generate_chart_image, which construct or render charts rather than diagnose an existing URL.

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?

It gives an explicit when: 'Use this before migrating an embed to find out what changes', with a concrete motivating example (a multi-axis URL supported only on a paid plan). It does not explicitly say when not to use it or name the sibling to use instead, so it stops short of full routing guidance.

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.