Skip to main content
Glama

Lokand Restaurant MCP

Set theme

set_theme
Destructive

Switch the site to a system theme with theme_id (lokand-base; get_site lists them; pages, sections and settings are kept). Legacy shape: a v1 theme_config patch (colors, fonts, hero title/subtitle) — prefer update_theme_settings, or get_style for a whole look. Revertible with revert_last_site_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": {
      "business_id": "<business_id>"
    },
    "name": "set_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
theme_idNoA system theme id from get_site (e.g. lokand-base)
business_idYes
theme_configNoLegacy: merge patch such as {"colors":{"primary":"#aa3300"},"fonts":{"heading":"..."}}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields 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)"
    • removedInput schema / properties / theme_key
      Removed value: -{
      -  "description": "Legacy: a style preset — terra, porto, noir, marche, slate",
      -  "enum": [
      -    "terra",
      -    "porto",
      -    "noir",
      -    "marche",
      -    "slate"
      -  ],
      -  "type": "string"
      -}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, idempotentHint=false and openWorldHint=true; the description adds real context beyond them by stating that pages, sections and settings are kept and that the operation is revertible via revert_last_site_change, which tempers the destructive flag meaningfully. It does not explain merge-patch overwrite behavior for the legacy shape, which is the riskiest part of the call.

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?

Dense but front-loaded — the primary path comes first, then the legacy path, then the revert note, with parenthetical hints doing routing work instead of prose. Slightly telegraphic in places ("lokand-base; get_site lists them"), but nothing is padding.

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 mutation tool with no output schema and an enormous nested `theme_config` schema, the description covers mode selection, parameter sourcing, side-effect preservation and undo, which is what an agent needs to call it safely. It omits any statement about response shape or what happens on an invalid theme_id, which is the remaining gap.

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?

Schema coverage is 67% and the description adds genuine meaning: `theme_id` is a system theme id sourced from get_site with a concrete example, and `theme_config` is framed as a legacy v1 patch limited to colors, fonts and hero title/subtitle with an alternative recommended. `business_id` is left undocumented, but its own schema entry is trivial.

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?

"Switch the site to a system theme with `theme_id`" is a specific verb+resource, and the description additionally carves out the legacy `theme_config` shape and names the tools to use instead (update_theme_settings, get_style), so an agent can tell the two modes and their siblings apart without opening the schema.

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?

Explicit routing: theme ids come from get_site, and for the legacy patch it says "prefer update_theme_settings, or get_style for a whole look," and it notes revert_last_site_change for undo. It stops short of stating when this tool should be chosen over the similarly named set_system_theme sibling, so guidance is strong but not exhaustive.

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