Skip to main content
Glama

Lokand Restaurant MCP

Theme rollback

theme_rollback
Destructive

Restore a custom theme's code to an earlier commit (Pro plan). It is saved as a new commit, so the rollback itself can be undone; on the live theme it goes live once compiled. Without commit, restores the version before the latest 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>",
      "theme_id": "<theme_id>"
    },
    "name": "theme_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
commitNoCommit hash from theme_history
theme_idYesA theme id from theme_list (or the system theme id lokand-base)
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / theme_id / description
      Previous value: -"A theme id from theme_list (or a system theme id: lokand-base, lokand-one)"New value: +"A theme id from theme_list (or the system theme id lokand-base)"
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=false, and the description adds real context beyond them: the rollback is persisted as a new commit, so it can itself be undone, and on a live theme it goes live once compiled. It also discloses the plan gating requirement, which no annotation conveys.

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, front-loaded with the action and plan requirement, then reversibility, then the commit-omitted default. Every clause carries information an agent needs and nothing repeats the annotations verbatim.

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 destructive mutation with no output schema, the description covers what changes, the plan gate, reversibility, and live-theme propagation. The remaining gap is business_id, which is neither described in the schema nor here, leaving one required parameter opaque.

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%, with business_id undocumented in the schema. The description compensates for the most consequential parameter by explaining the omitted-commit default ("restores the version before the latest change"), which the schema only implies via optionality, though business_id remains unexplained everywhere.

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 verb and resource: "Restore a custom theme's code to an earlier commit", with a clear scope qualifier (custom themes, Pro plan). It is unmistakably distinct in effect from theme_delete or theme_publish, but it never names a sibling, so routing is inferred rather than stated.

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?

Usage context is clear: roll back to a specific commit, or omit the commit to revert the last change, and the schema points to theme_history as the source of the hash. It does not state when-not to use it (e.g., versus theme_pull or theme_sync) or any prerequisite beyond the Pro plan note.

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