Skip to main content
Glama

Lokand Restaurant MCP

Update theme

update_theme
Destructive

Legacy look op: patch v2-style tokens (colors, fonts, radius, hero layout, …) or set custom CSS. Prefer update_theme_settings.

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": "update_theme"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokensNoMerge patch on theme tokens: colors{primary,accent,bg,fg,primaryFg,card,muted,line,line2}, loyalty{bg,ink}, fonts{heading,body,mono}, radius, radiusButton, heroLayout, serif, density, headingCase, buttonStyle, reserveKind. null removes an override.
custom_cssNoExtra CSS; null clears it. No @import, url() or <
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / preset
      Removed value: -{
      -  "description": "Style preset: terra | porto | noir | marche | slate",
      -  "maxLength": 40,
      -  "type": "string"
      -}
  2. First observed

TDQS

A3.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, and the description adds nothing about what gets overwritten, whether the patch can be reverted, or the consequences of a destructive call. The only extra signal is the 'Legacy' tag and the preference pointer, which are usage rather than behavioral disclosure. There is no contradiction with the annotations, but for a destructive mutation the description does not go beyond them.

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 with the legacy status and the actionable payload leading, and the routing advice second. No filler and nothing an agent must read twice.

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 destructive, non-idempotent nested-object mutation with no output schema, the definition gives the payload shape and the sibling to prefer but omits outcome behavior (partial patch failures, whether custom_css replaces all prior CSS). The schema carries the null-clearing semantics, but the description leaves the destructive consequences underspecified.

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 67% and the schema itself already enumerates the token groups (colors, fonts, radius, hero layout) with the merge-patch and null-removal semantics. The description only restates those categories, adding 'v2-style' as a version qualifier, so it contributes nothing new about the remaining undocumented parameter detail.

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 specific verbs ('patch', 'set') on a named resource ('v2-style tokens', 'custom CSS') and labels the tool 'Legacy look op'. It distinguishes itself from update_theme_settings by naming it as the preferred alternative, though the resource ('theme') is only implied by the tool name and title.

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 guidance: 'Prefer update_theme_settings' tells the agent to reach for the sibling first, with the legacy path reserved for token patching or custom CSS. It lacks an explicit when-not condition (e.g., 'only use when update_theme_settings cannot express the tokens'), but the alternative is clearly stated.

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