Skip to main content
Glama

Charts by Szum

by io.szum
OverviewDiscussionsAdmin

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
NameRequiredDescriptionDefault
qNoCase-insensitive title substring search; trimmed and limited to 100 characters
sortNoSort by creation time (default), update time, or title A-Z
limitNoPage size; defaults to 100 and has a maximum of 1000
cursorNoOpaque nextCursor from the previous page
sourceNoFilter by one or more chart sources; omit to list all

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemsYes
totalNoExact match count, present only for title searches
nextCursorYesOpaque cursor for the next page, or null on the last page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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}$"
  2. Changed2 schema fields changed
    • 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"
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description adds critical behavioral details: requires authentication, returns paginated metadata (not configs), and explains draft-only chart properties (publishedAt null, hasDraft true, sizeBytes 0). No contradictions with 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 two sentences with no redundant information. It front-loads the purpose and then provides essential behavioral details, achieving high conciseness.

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 output schema exists and parameters are well-documented in the schema, the description adequately covers purpose, authentication, and special response field behavior. No gaps remain for effective tool selection.

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%, so the baseline is 3. The description does not add parameter-specific meaning beyond the schema's own descriptions; the behavioral details about drafts pertain to output fields, not input 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 clearly states the tool lists charts from the user's saved library, distinguishes from siblings like get_chart and get_chart_config by noting it returns metadata and URLs not configs, making the purpose 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 explicitly says 'Use this when the user wants to find charts', providing clear context. However, it lacks explicit exclusions or alternatives to sibling tools, which prevents a higher score.

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