Charts by Szum

List chart versions

list_chart_versions

Read-only

Use this when the user wants to see a saved chart's earlier publications, find one to read with get_chart_document, or pick one to restore with restore_chart_version. Returns versions newest first with who published each, from where and what changed; requires authentication.

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": "list_chart_versions"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Opaque 32-character saved-chart id
`limit`	No	Page size; defaults to 100 and has a maximum of 1000
`named`	No	List only versions that were given a name
`cursor`	No	Opaque nextCursor from the previous page

Output Schema

Name	Required	Description
`items`	Yes
`nextCursor`	Yes	Opaque cursor for older versions, or null on the last page
`currentVersionNumber`	Yes	Number of the version the chart publishes now, or null for a chart that was never published

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 2, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, non-destructive, and closed-world, so safety is covered. The description still adds real context beyond them: newest-first ordering, that each entry carries who published it, from where, and what changed, plus an explicit authentication requirement. Minor gap: no mention of pagination limits despite cursor/limit params.

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?

A single dense sentence that front-loads the use case before the return-shape note, with no repetition of the title or schema. Every clause carries information the agent would otherwise have to guess.

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 read-only list tool with a full output schema and 100%-documented params, the description covers the missing pieces: when to choose it, what the results contain, ordering, and auth. Nothing an agent needs to call it correctly is absent.

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 100%, so id format, limit bounds, cursor semantics, and the named filter are all fully documented in the schema. The description adds nothing about parameters, so the baseline 3 applies rather than more.

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?

States a specific verb and resource (list a saved chart's versions) and immediately scopes it to 'earlier publications,' which separates it from get_chart, get_chart_document, and list_charts. The two named sibling references make the boundary unambiguous.

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

Usage Guidelines5/5

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

Explicitly gives the three triggering intents: browse past publications, find one to read with get_chart_document, or pick one to restore with restore_chart_version. This routes the agent to the correct downstream tool rather than leaving it to inference.

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

All Charts by Szum tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?