Skip to main content
Glama

Lokand Restaurant MCP

Update theme settings

update_theme_settings
Destructive

Merge-patch the theme's global settings (keys from get_site.theme.theme_settings, e.g. color_primary, font_heading, radius, custom_css). null resets a key to the theme default.

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>",
      "settings": "<settings>"
    },
    "name": "update_theme_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
settingsYesMerge patch on the theme's global settings
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and non-idempotent, but the description adds genuinely new semantics: it is a merge patch (so unspecified keys are retained) and passing null resets a key to the theme default, which explains why it is destructive. It stops short of covering permissions or the effect on the live published 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?

Two dense sentences with the operation and its key source front-loaded, followed by the one non-obvious value rule (null reset). No filler or restatement of the title.

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 two-parameter tool with an open-ended nested object and no output schema, the description supplies the critical context: where keys come from, examples, and null semantics. It is slightly incomplete on business_id and on whether changes affect the published theme.

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 50% and the settings description merely repeats 'merge patch', but the description goes further by enumerating plausible key names, pointing to get_site.theme.theme_settings as the authoritative key source, and defining null as a reset-to-default value. business_id remains unexplained in both places.

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 states a specific operation and target: 'Merge-patch the theme's global settings', with concrete example keys (color_primary, font_heading, radius, custom_css). This distinguishes it from the broader update_theme or theme_write_files by scoping to global settings, though it never names an alternative explicitly.

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: the agent learns valid keys come from get_site.theme.theme_settings, which hints at a read-then-patch workflow. There is no explicit when-to-use or when-not guidance relative to update_theme, set_theme, or theme_write_files, so the agent must infer the boundary.

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