Skip to main content
Glama

Lokand Restaurant MCP

Revert last site change

revert_last_site_change
Destructive

Undo the most recent site change made through the site ops or set_theme (up to the last 10, kept for 30 days). Call repeatedly to step further back. 404 when there is nothing to undo.

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

Input Schema

NameRequiredDescriptionDefault
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds genuinely new behavior: a bounded history of 10 changes retained 30 days, the step-back-by-repetition model, and the 404 exhaustion signal. It does not say whether reverts are scoped per-user or what state is restored, but it goes well beyond the structured hints.

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 short sentences with zero waste: the core action first, then the iteration model, then the failure case. Every sentence carries information an agent needs.

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 one-parameter destructive tool with no output schema, the description covers the history window, repeatability, and the 404 terminal condition — which is most of what a caller needs. Remaining ambiguity (auth scoping, what exactly is restored) is minor for this complexity level.

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 0% and the single business_id parameter is undocumented in both schema and description. The parameter is self-explanatory by name, so this is not a serious gap, but the description contributes nothing about it and therefore does not compensate for the coverage.

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 action (undo the most recent site change) and bounds the scope precisely: changes made through site ops or set_theme. An agent can tell this apart from set_theme or apply_site_preset because it is framed as an inverse operation rather than a mutation.

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?

Says how to use it iteratively ('call repeatedly to step further back') and what happens when exhausted (404 when there is nothing to undo). It stops short of explicit exclusions (e.g., do not use to undo menu/item edits), but the clear context is enough to select it confidently.

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