Charts by 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

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

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.

Changed3 schema fields changedOct 21, 2026
- removedOutput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / view / const
```
Removed value: -"saved-chart"
```
- addedOutput schema / properties / view / examples
```
Added value: +[
+  "saved-chart"
+]
```

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.0

Behavior4/5

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

Annotations already declare non-read-only, non-destructive, closed-world behavior. The description adds two things the annotations don't: an authentication requirement and the guarantee that publication state and public URLs are left intact — meaningful mutation-safety context for an agent.

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 front-loaded sentence with the trigger first and the non-effects second; every clause carries information and nothing is redundant.

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?

An output schema exists and parameters are fully documented, so the description only needs the operational context it supplies: auth requirement and mutation scope. It doesn't mention behavior on invalid/duplicate titles or whether the new title is returned, but those are minor given the rich structured fields.

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%, with id format constraints and title trimming/length limit already documented. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

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?

States a specific verb ('change a saved chart's library title') and resource, and scopes out what is untouched (document, publication state, public URLs). That scoping implicitly distinguishes it from update_chart/save_chart, but no sibling is named explicitly.

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?

Opens with an explicit trigger ('Use this when the user wants to change ... title') and enumerates what it does not affect, which effectively tells the agent when to prefer it over a broader update. It stops short of naming an alternative tool outright.

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?