Charts by Szum

Get chart

get_chart

Read-only

Use this when the user identifies a saved chart by id and wants to view it or retrieve its metadata and URLs. Displays the published chart when available and does not return its document; requires authentication.

Input Schema

Name	Required	Description	Default
`id`	Yes	Opaque 32-character saved-chart id

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 18, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish read-only, non-destructive behavior, and the description adds useful context: authentication is required, the published chart is displayed when available, and the document itself is not returned. It does not need to explain return values because an output schema exists.

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 description is two tight sentences, front-loaded with the usage condition and followed by key behavioral constraints. There is no redundant or wasted phrasing.

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?

Given the simple one-parameter schema, full schema coverage, existing annotations, and an output schema, the description provides enough context: when to use it, what it returns conceptually, that documents are excluded, and that authentication is required.

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?

With one parameter and 100% schema description coverage, the schema already documents the opaque 32-character chart id. The description reinforces that the id is for a saved chart but adds no syntax or format detail beyond the schema.

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: retrieve a saved chart by id to view it or get metadata and URLs. It also distinguishes this tool from a sibling by explicitly saying it 'does not return its document,' contrasting with get_chart_document.

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 a clear usage trigger: the user identifies a saved chart by id and wants to view or retrieve metadata/URLs. The exclusion around documents implies when to use get_chart_document instead, though it does not name that alternative explicitly.

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?