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 documents; requires authentication. Draft-only editor charts have publishedAt null, hasDraft true, and sizeBytes 0 because sizeBytes measures only the stored published document, 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 for title searches or when explicitly requested
nextCursorYesOpaque cursor for the next page, or null on the last page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • removedOutput schema / properties / items / items / properties / configUrl
      Removed value: -{
-  "description": "Owner-only chart-config endpoint",
-  "type": "string"
-}
    • addedOutput schema / properties / items / items / properties / documentUrl
      Added value: +{
+  "description": "Owner-only chart-document endpoint",
+  "type": "string"
+}
    • changedOutput schema / properties / items / items / properties / hasDraft / description
      Previous 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"New value: +"Whether an unpublished editor document exists; with sizeBytes 0 the chart is draft-only, otherwise it has unpublished edits alongside a stored published document"
    • removedOutput schema / properties / items / items / properties / publishedAt / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / items / items / properties / publishedAt / type
      Added value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / items / items / 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 / properties / items / items / required
      Previous value: -[
-  "id",
-  "source",
-  "title",
-  "createdAt",
-  "updatedAt",
-  "sizeBytes",
-  "publishedAt",
-  "imageUrl",
-  "embedUrl",
-  "configUrl",
-  "hasDraft"
-]New value: +[
+  "id",
+  "source",
+  "title",
+  "createdAt",
+  "updatedAt",
+  "sizeBytes",
+  "publishedAt",
+  "imageUrl",
+  "embedUrl",
+  "documentUrl",
+  "hasDraft"
+]
    • removedOutput schema / properties / nextCursor / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / nextCursor / type
      Added value: +[
+  "string",
+  "null"
+]
    • changedOutput schema / properties / total / description
      Previous value: -"Exact match count, present only for title searches"New value: +"Exact match count, present for title searches or when explicitly requested"
  2. 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}$"
  3. 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"
  4. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds that authentication is required, that results are paginated, and explains the draft-only chart field semantics (publishedAt null, hasDraft true, sizeBytes 0). These are non-obvious behaviors beyond the schema, adding real value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences with front-loaded purpose and no filler. The explanation about draft charts is a single clause that justifies the sizeBytes anomaly, which is valuable. It is concise and well-structured.

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?

Given the output schema and fully described input schema, the description covers the main usage, authentication, return type, and a subtle data nuance. It does not mention rate limits or default sort order, but those are minor given the schema already documents defaults. It is complete for an agent to call the tool correctly.

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 all parameters are already documented. The tool description does not add any parameter-specific meaning or examples, so it relies on the schema. No harm, but no added value 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 ('find charts') and resource ('saved library'), and explicitly clarifies it returns metadata/URLs not documents, distinguishing it from get_chart_document. This makes its purpose unambiguous and distinct from siblings.

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 explicitly says 'Use this when the user wants to find charts in their saved library,' giving a clear trigger. It implicitly excludes the case of needing the document by stating it returns metadata/URLs, though it does not name alternative tools for those cases. Clear context without explicit exclusions.

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