Skip to main content
Glama

Lokand Restaurant MCP

Apply template

apply_template
Destructive

Rebuild the site's pages and sections from a segment template (cafe, ghost-kitchen, fine-dining, chain, bar, bakery — see get_site.templates). Replaces the page structure; hero copy and custom CSS carry over. keep_theme=true keeps the current style. Revertible with revert_last_site_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>",
      "template": "<template>"
    },
    "name": "apply_template"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateYescafe | ghost-kitchen | fine-dining | chain | bar | bakery
keep_themeNoKeep the current style instead of the template's (default false)
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds materially useful detail beyond them: what exactly gets replaced (page structure), what survives (hero copy and custom CSS), how keep_theme alters the outcome, and how destruction can be undone. That is precisely the disclosure an agent needs before invoking a destructive, non-idempotent operation.

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 tight sentences with the destructive action front-loaded, followed by carry-over semantics and the undo path. No redundant framing or filler, and each sentence contributes a distinct fact.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, non-idempotent mutation with no output schema, the definition covers what changes, what is preserved, a parameter's effect, and the recovery mechanism. Nothing an agent needs in order to call this safely is missing.

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?

The description clarifies keep_theme=true behavior and enumerates template values, but the schema already carries 67% coverage including a description on keep_theme and the full enum, so much of this is restated. The business_id parameter receives no explanation in either place, though it is self-evident from the tool context.

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 concrete verb and resource — 'Rebuild the site's pages and sections from a segment template' — and enumerates the six valid segment templates, so an agent knows exactly what this operates on. It immediately distinguishes itself from lighter alternatives like apply_style_preset or apply_site_preset by scoping to full page/section structure.

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 clear context for use and names the follow-up alternative 'revert_last_site_change' as the undo path, plus points to get_site.templates as the authoritative source of template values. It stops short of explicitly contrasting with apply_site_preset or apply_country_settings, so the when-not comparison is left implicit.

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