szum

List charts

list_charts

Read-only

Use this when the user wants to find charts in their saved library. Returns paginated metadata and URLs, not chart configs; requires authentication. Draft-only editor charts have publishedAt null, hasDraft true, and sizeBytes 0 because sizeBytes measures only the stored published config, not draft storage.

Input Schema

TableJSON Schema

Name	Required	Description
`q`	No	Case-insensitive title substring search; trimmed and limited to 100 characters
`sort`	No	Sort by creation time (default), update time, or title A-Z
`limit`	No	Page size; defaults to 100 and has a maximum of 1000
`cursor`	No	Opaque nextCursor from the previous page
`source`	No	Filter by one or more chart sources; omit to list all

Output Schema

TableJSON Schema

Name	Required	Description
`items`	Yes
`total`	No	Exact match count, present only for title searches
`nextCursor`	Yes	Opaque cursor for the next page, or null on the last page

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedJul 18, 2026
- changedOutput schema / properties / items / items / properties / id / description
```
Previous value: -"Opaque saved-chart id"New value: +"Opaque 32-character saved-chart id"
```
- addedOutput schema / properties / items / items / properties / id / pattern
```
Added value: +"^[0-9a-f]{32}$"
```

Changed2 schema fields changedJul 18, 2026

changedOutput schema / properties / items / items / properties / hasDraft / description

Previous value: -"Whether the chart has unpublished edits"New value: +"Whether an unpublished editor config exists; with sizeBytes 0 the chart is draft-only, otherwise it has unpublished edits alongside a stored published config"

changedOutput schema / properties / items / items / properties / sizeBytes / description

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

AddedJul 18, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds critical behavioral details: requires authentication, and explains the behavior for draft-only editor charts (publishedAt null, hasDraft true, sizeBytes 0). This adds significant value beyond annotations.

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 concise and front-loaded with the usage instruction. It consists of two sentences, each adding essential information with no filler. Every sentence earns its place.

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 tool has 5 optional parameters, full schema coverage, and an output schema (not shown but indicated), the description covers purpose, authentication, and notable edge cases. It is complete enough for an AI agent to use correctly without additional context.

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 baseline is 3. The description does not add extra meaning beyond the schema; it mentions pagination implicitly but does not explain individual parameters. However, the schema is self-sufficient, so a 3 is appropriate.

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 clearly states the tool's purpose: to list charts from the user's saved library. It specifies the return type (paginated metadata and URLs, not chart configs) and prerequisites (authentication). This clearly distinguishes it from sibling tools like get_chart or get_chart_config.

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 explicitly states when to use the tool ('when the user wants to find charts'), providing clear context. It does not explicitly list when not to use it or name alternatives, but the sibling tool list and the tool's purpose imply differentiation.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation4/5

Most tools have clearly distinct purposes, but get_chart and get_chart_config are both retrieval-by-id operations that require careful reading to distinguish metadata/URLs from config. Additionally, get_preview_state is somewhat cryptic despite its description, but overall overlap is minimal.

Naming Consistency5/5

All 13 tool names follow a consistent verb_noun pattern in lowercase snake_case (e.g., delete_chart, get_chart_config, list_themes). There are no deviations or mixed conventions, making the naming predictable and coherent.

Tool Count5/5

With 13 tools, the server is well-scoped for a charting service. Each tool serves a distinct role in the workflow (reference, validation, CRUD, rendering), and the count is neither sparse nor overwhelming, fitting within the ideal 3-15 range.

Completeness5/5

The tool surface covers the full chart lifecycle: create (save_chart), read (get_chart, get_chart_config, list_charts), update (update_chart, rename_chart), and delete (delete_chart). It also includes validation, rendering, reference data (examples, marks, themes), and preview state restoration, addressing practical needs. Minor gaps like explicit draft management are indirectly handled through update_chart's safeguards.

Resources

Need Help?