Skip to main content
Glama

Lokand Restaurant MCP

Set system theme

set_system_theme
Destructive

Switch to another system theme (get_site lists system_themes). Pages, sections and settings are kept.

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": {
      "business_id": "<business_id>",
      "theme_id": "<theme_id>"
    },
    "name": "set_system_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
theme_idYesA system theme id from get_site (e.g. lokand-base)
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / theme_id / description
      Previous value: -"A system theme id from get_site (e.g. lokand-base, lokand-one)"New value: +"A system theme id from get_site (e.g. lokand-base)"
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety bar is partially covered. The description adds real behavioral value by stating that pages, sections and settings survive the switch, which scopes the destruction; it still doesn't say what is lost or whether the switch is reversible.

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 short sentences, zero filler, with the action stated first and the preservation guarantee second. Every clause carries information the agent needs.

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 non-idempotent, destructive mutation with no output schema and a half-documented schema, the definition covers the main worry (what is kept) but omits permissions, reversibility, and the fate of theme-specific customizations. Adequate, but not complete for a destructive operation.

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%: theme_id is already documented in the schema with an example, while business_id is undocumented in both places. The description reinforces where theme_id values originate (get_site's `system_themes`) but adds no meaning for business_id, so it neither fully compensates nor is empty.

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 uses a specific verb and resource ("Switch to another system theme") and names the prerequisite listing source (get_site's `system_themes`). It does not, however, explain how it differs from nearby siblings like set_theme or update_theme, leaving that distinction to schema inspection.

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 gives a clear usage context by pointing the agent at get_site as the source of valid system theme ids, which is the key precondition for calling this tool. It stops short of explicit when-not guidance or naming alternative theme-setting tools.

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