Skip to main content
Glama

Lokand Restaurant MCP

Theme sync

theme_sync
Destructive

Compile the latest commit on a custom theme's main branch now (Pro plan). Pushes compile on their own; call this to apply a push immediately or to retry. Validates like an upload and, for the live theme, publishes once compiled. Poll theme_get for status.

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_sync"
  }
}

Input Schema

NameRequiredDescriptionDefault
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
Behavior4/5

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

The annotations already declare it as non-read-only, non-idempotent, and destructive, and the description adds useful context: it compiles the latest commit, validates like an upload, publishes live themes after compilation, and requires polling theme_get for status. It does not spell out failure behavior or exactly what makes it destructive, but the added operational detail is substantial.

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?

Four short sentences, front-loaded with the core action and followed by the key usage, side effects, and follow-up. No sentence is redundant.

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?

Given the rich annotations and no output schema, the description is largely complete: it explains when to call, what compilation/publishing does, and where to check status. The remaining gap is that required business_id is unexplained, and failure behavior is not described.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: theme_id is documented in the schema, but business_id has no description in either the schema or the tool description. The description itself adds no parameter-level meaning beyond mentioning custom themes and their main branch.

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?

The description states a specific action and resource: compile the latest commit on a custom theme's main branch now. It clearly distinguishes this from normal push-triggered compilation and explains the immediate-apply/retry use case.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly says pushes compile on their own, so this tool is for applying a push immediately or retrying. It also directs the agent to poll theme_get for status and notes the Pro plan requirement.

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