Skip to main content
Glama

Lokand Restaurant MCP

Update site

update_site
Destructive

Low-level escape hatch: apply an RFC 7386 JSON merge patch to the whole v3 site document returned by get_site.document (objects merge, null deletes a key, arrays REPLACE). Prefer the specific site ops. The result is validated against the theme before anything is saved.

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>",
      "patch": "<patch>"
    },
    "name": "update_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchYesRFC 7386 JSON merge patch on the whole theme data document
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=false, and the description adds genuinely new behavioral facts: merge semantics where objects merge, null deletes a key, and arrays REPLACE (an easy data-loss trap), plus the guarantee that the result is validated against the theme before anything is saved. It does not cover permissions or whether a separate publish step is required to make changes live.

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?

Three sentences, front-loaded by the escape-hatch framing, then the mechanism, then the safety guarantee. No filler and no repetition 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 destructive whole-document mutation with no output schema, the definition supplies the mechanism, the data-loss semantics, and the validation-before-save behavior. The notable remaining gap is the relationship to publish_site — whether a validated patch is live immediately or requires a separate publish call.

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?

The patch parameter's schema line only repeats 'RFC 7386 JSON merge patch'; the description actually explains the operator semantics (merge, delete via null, array replacement), which is the information an agent needs to construct a correct nested patch. business_id remains undocumented and patch's nested free-form structure is only loosely characterized.

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?

States a specific verb, resource, and mechanism: apply an RFC 7386 JSON merge patch to the whole v3 site document obtained from get_site.document. The framing as a 'low-level escape hatch' plus 'Prefer the specific site ops' cleanly separates it from siblings like update_block, update_section, and update_theme.

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?

Gives explicit when-to-use routing ('prefer the specific site ops') and positions itself as a fallback, which is the key decision an agent must make. It stops short of naming which specific op covers common edits (blocks, sections, theme settings), so the agent must inspect sibling names to act on the guidance.

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