Skip to main content
Glama

Set colours and fonts

set_theme
DestructiveIdempotent

Changes the site's colour palette and tone (which sets the heading font). Only the fields given change.

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": {
      "site_id": "<site_id>",
      "theme": "<theme>"
    },
    "name": "set_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
themeYes
site_idYesThe site id from list_sites or create_site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description contributes a genuinely useful behavioural fact — 'Only the fields given change' — clarifying partial-update semantics. It does not, however, explain what is destroyed or whether live/published sites are affected, which matters given destructiveHint=true.

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?

Two short clauses, front-loaded with the action and resource, with no filler. The parenthetical is slightly redundant with the schema but is defensible as it surfaces a non-obvious side effect.

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 two-parameter nested mutation with no output schema and a destructive annotation, the description covers what changes but not the consequences: whether a published site is instantly restyled, whether changes are reversible, or what is returned. Adequate but with clear gaps an agent would want filled.

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 50%, with site_id documented in the schema and the nested theme object undocumented at the top level. The description names the two updatable fields (palette, tone) and the partial-update rule, but adds no enum values or format guidance beyond what the schema already says, including the heading-font note which is duplicated verbatim in the schema.

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 and resource: changes the site's colour palette and tone, and clarifies that tone drives the heading font. An agent can distinguish this from a general update_site, though the description never names that sibling explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use guidance at all: nothing says whether to prefer set_theme over update_site for appearance changes, nor any precondition such as the site needing to exist or be unpublished. The only usable hint is the implicit 'use this for palette/tone' framing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources