Skip to main content
Glama

apply_theme

Applies a built-in theme to the open map, updating colours, textures, and label presets to match a chosen visual style.

Instructions

Apply a built-in theme (colours, textures, label presets) to the open map.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does reveal that the target is implicitly the open map (no map id needed), but it does not say whether applying a theme overwrites existing colours/labels, whether it is reversible via undo, or what happens if the named theme does not exist.

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 front-loaded sentence with the action first and the parenthetical clarifying scope without waste. Nothing is repeated or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, no-output-schema tool this is close to adequate, but two things an agent needs are missing: how to discover valid theme names and whether the operation replaces existing map styling. The implicit target (open map) is at least stated.

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

Parameters2/5

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

Schema coverage is 0% for the single 'name' parameter and there is no enum. The description adds only that the name refers to a built-in theme, but gives no source of valid values (e.g. list_themes), no format hints, and no case/identifier convention.

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?

States a specific verb (apply) and resource (theme), and clarifies what a theme contains (colours, textures, label presets) and where it lands (the open map). It does not name or differentiate from the likely companion list_themes, so an agent must infer that discovery is a separate call.

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 only implied: the tool acts on the currently open map, and the word 'built-in' narrows the acceptable input to preset themes rather than custom ones. There is no explicit when-to-use versus alternatives (e.g. recolor_symbols, paint_ground, set_frame) and no pointer to list_themes for obtaining valid names.

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