szum

Rename chart

rename_chart

Use this when the user wants to change a saved chart's library title without changing its document, publication state, or public URLs; requires authentication.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Opaque 32-character saved-chart id
`title`	Yes	New saved-chart title; trimmed and limited to 200 characters

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Opaque 32-character saved-chart id
`view`	Yes
`title`	Yes	Saved chart title
`source`	Yes	Chart origin; an open set of string values
`editUrl`	Yes
`embedUrl`	Yes	Interactive-embed URL
`imageUrl`	Yes	Rendered-image URL
`createdAt`	Yes	ISO-8601 creation timestamp
`manageUrl`	Yes
`sizeBytes`	Yes	Compressed size of the stored published document, excluding drafts; 0 means no published document has been stored yet
`updatedAt`	Yes	ISO-8601 last-update timestamp
`documentUrl`	Yes	Owner-only chart-document endpoint
`publishedAt`	Yes	ISO-8601 publish timestamp, or null when public URLs are dark

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedSep 26, 2026

removedOutput schema / properties / configUrl

Removed value: -{
-  "description": "Owner-only chart-config endpoint",
-  "type": "string"
-}

addedOutput schema / properties / documentUrl

Added value: +{
+  "description": "Owner-only chart-document endpoint",
+  "type": "string"
+}

removedOutput schema / properties / publishedAt / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedOutput schema / properties / publishedAt / type
```
Added value: +[
+  "string",
+  "null"
+]
```

changedOutput schema / properties / sizeBytes / description

Previous value: -"Compressed size of the stored published config, excluding drafts; 0 means no published config has been stored yet"New value: +"Compressed size of the stored published document, excluding drafts; 0 means no published document has been stored yet"

changedOutput schema / required

Previous value: -[
-  "view",
-  "id",
-  "source",
-  "title",
-  "createdAt",
-  "updatedAt",
-  "sizeBytes",
-  "publishedAt",
-  "imageUrl",
-  "embedUrl",
-  "configUrl",
-  "editUrl",
-  "manageUrl"
-]New value: +[
+  "view",
+  "id",
+  "source",
+  "title",
+  "createdAt",
+  "updatedAt",
+  "sizeBytes",
+  "publishedAt",
+  "imageUrl",
+  "embedUrl",
+  "documentUrl",
+  "editUrl",
+  "manageUrl"
+]

AddedJul 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate this is a mutating (readOnlyHint=false) but non-destructive (destructiveHint=false) operation. The description adds valuable context by guaranteeing that the document, publication state, and public URLs are unaffected, and by flagging the authentication requirement.

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?

The entire description is a single sentence with no filler. The usage trigger is front-loaded, and every clause adds either scope, exclusion, or a prerequisite.

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 simple two-parameter rename operation with an output schema and annotations covering mutation/safety, the description is complete. It covers purpose, when to use it, what it does not affect, and the authentication requirement.

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 the baseline is 3. The description adds meaning beyond the schema by clarifying that 'title' refers to the library title (not the document title) and that the operation affects only that field, which helps the agent understand the semantic scope of both parameters.

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: 'change a saved chart's library title'. It also distinguishes itself from siblings by explicitly listing what it does not change ('document, publication state, or public URLs'), making the tool's scope unambiguous.

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 description opens with 'Use this when the user wants to change a saved chart's library title', which is an explicit trigger condition. It also provides exclusions ('without changing its document, publication state, or public URLs') and a prerequisite ('requires authentication'), though it does not name alternative tools such as update_chart.

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

All 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?