Skip to main content
Glama
Sign In

ChartAnt

by net.chartant
OverviewDiscussionsAdmin

Restore chart version

restore_chart_version
Idempotent

Make an earlier version of a living chart the current one again (the version in between stays in the history, so this can be undone). Its link shows the restored version and attached destinations get a fresh copy. Needs a connection signed in to a free account (connector URL ending in /mcp/account).

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>",
      "version": "<version>"
    },
    "name": "restore_chart_version"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe chart id from create_living_chart or list_my_charts.
versionYesThe version number from list_chart_versions.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

It adds substantial behavior beyond the annotations: intermediate versions stay in history so the restore is undoable, the link reflects the restored version, attached destinations receive a fresh copy, and a free-account connection (connector URL ending in /mcp/account) is required. Those are exactly the side effects and auth prerequisites an agent needs before invoking a mutation.

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 tight sentences, front-loaded with the core action, followed by side effects and then the auth prerequisite. The parenthetical aside and the slightly ambiguous 'Its link' are minor blemishes, but no sentence is wasted.

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?

For a two-parameter mutation with no output schema, the description covers undoability, downstream destination effects, and the account requirement, which is nearly everything an agent needs. It stops short of describing the returned object, but the link behavior gives a reasonable hint.

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 coverage is 100% and both parameters are documented at the schema level, including where the id and version come from. The description adds no format or constraint detail beyond what the schema already provides, so the baseline 3 applies.

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: 'Make an earlier version of a living chart the current one again.' That is clearly distinct from create_living_chart, update_living_chart, and list_chart_versions, so an agent can tell what this tool does without opening the schema.

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 revert use case is stated plainly, and the schema ties the 'version' input to list_chart_versions, so the agent can infer the preceding step. It does not explicitly say when to prefer this over update_living_chart, but the context is clear enough that no exclusion is needed.

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

All ChartAnt toolsInspect
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