szum

List themes

list_themes

Read-only

Use this when choosing a visual theme for a chart. Returns every built-in theme with guidance on where each works best and, when signed in, the workspace's shared themes.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_themes"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`themes`	Yes
`workspaceThemes`	No	The signed-in workspace's shared themes. Pass a name as sharedTheme to render_chart, save_chart, or update_chart.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 21, 2026
- removedOutput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / themes / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / themes / items / properties / name / enum
```
Removed value: -[
-  "editorial",
-  "clean",
-  "noir",
-  "loud",
-  "soft",
-  "technical"
-]
```
- addedOutput schema / properties / themes / items / properties / name / examples
```
Added value: +[
+  "editorial",
+  "clean",
+  "noir",
+  "loud",
+  "soft",
+  "technical"
+]
```
- removedOutput schema / properties / workspaceThemes / items / additionalProperties
```
Removed value: -false
```

Changed2 schema fields changedOct 21, 2026

addedOutput schema / properties / themes / items / properties / isDefault

Added value: +{
+  "description": "When signed in, whether new charts in the workspace start with it",
+  "type": "boolean"
+}

addedOutput schema / properties / workspaceThemes

Added value: +{
+  "description": "The signed-in workspace's shared themes. Pass a name as sharedTheme to render_chart, save_chart, or update_chart.",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "description": {
+        "type": "string"
+      },
+      "isDefault": {
+        "description": "Whether new charts in the workspace start with it",
+        "type": "boolean"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "description",
+      "isDefault"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedJul 21, 2026
- addedOutput schema / properties / themes / items / properties / name / enum
```
Added value: +[
+  "editorial",
+  "clean",
+  "noir",
+  "loud",
+  "soft",
+  "technical"
+]
```

Changed1 schema field changedJul 11, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "themes": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "name",
+          "description"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "themes"
+  ],
+  "type": "object"
+}

First observedApr 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that: it discloses a conditional result set (shared themes only appear when the caller is signed in), which is not captured anywhere in the structured fields.

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?

Two sentences, zero waste, with the invocation trigger front-loaded before the return description. Every clause carries information an agent would not otherwise have.

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?

With an output schema handling return shape, annotations handling safety, and no parameters, the description only needs to state the trigger and the auth-conditional scope – both are present. Nothing needed to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and there is no schema semantics for the description to compensate for. The mention of 'when signed in' usefully signals that output varies with ambient auth state rather than with inputs.

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?

States a specific verb (list) and resource (themes) plus the content returned: every built-in theme with usage guidance, and shared workspace themes when signed in. An agent can immediately distinguish this from chart-mutation siblings like update_chart or render_chart.

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?

"Use this when choosing a visual theme for a chart" gives a clear selecting condition for invocation. It doesn't name an alternative, but no sibling tool covers themes, so there is nothing to route away from.

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

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?