Skip to main content
Glama

list_themes

List built-in Wonderdraft theme names so you can choose a valid theme when creating a new map or applying a theme.

Instructions

Names of the built-in themes usable with new_map / apply_theme.

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

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses little beyond the payload. 'Built-in' usefully signals that only predefined themes are covered (not user-defined ones), but it says nothing about read-only semantics, whether the list is complete or paginated, or what an unknown/absent theme means for apply_theme.

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?

A single compact sentence with no filler, front-loading the returned artifact before the consumers. Nothing is wasted.

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?

For a zero-parameter list tool with no output schema, the description adequately implies the return value ('names of the built-in themes'). A brief note on completeness of the list would make it fully self-sufficient, but nothing essential to invoking it 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?

Zero parameters, so the baseline of 4 applies. The description also correctly frames the values as input to new_map/apply_theme, adding light meaning about how the output is consumed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (built-in themes) and what is returned (their names), and it ties the resource to the two siblings that consume it, new_map and apply_theme. An agent can distinguish this discovery tool from the mutating tools without opening the schema, though the verb 'list' is only implied by the title rather than stated outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: by naming new_map and apply_theme as consumers, it hints that this should be called first to discover valid theme names. It never explicitly says 'call this before X' or states that no other way exists to obtain valid theme values, so the guidance requires inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.