Skip to main content
Glama

Lokand Restaurant MCP

Apply site preset

apply_site_preset
Destructive

Alias of apply_template (preset = template id).

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>",
      "preset": "<preset>"
    },
    "name": "apply_site_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
presetYescafe | ghost-kitchen | fine-dining | chain | bar | bakery
keep_themeNo
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already flag this as destructive, non-idempotent, and open-world, so the description's real burden is to say what gets destroyed or overwritten and whether existing site configuration is replaced. Instead it offers nothing beyond the alias relationship, so the most important behavioral facts for a destructive call are left to the annotations alone.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler, which is structurally clean and front-loaded. However, brevity here reflects under-specification rather than economy; the one line spent on an alias relationship could have been spent on the operation's effect.

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

Completeness2/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 and only partial parameter documentation, the definition leaves out what the preset changes, whether prior site content is lost, and how to recover. Given the tool's risk profile, this is well short of complete.

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 33%, so the description should compensate for undocumented `keep_theme` and `business_id`, and it does not. Worse, the one parameter note it does give (`preset` = template id) conflicts with the schema, where `preset` is an enum of business types (cafe, bar, bakery, etc.), potentially misleading an agent about what value to pass.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description defines the tool only by reference to a sibling ("Alias of apply_template") rather than stating a verb+resource of its own, and it never explains what applying a preset actually does to a site. The parenthetical hint about `preset` gives a partial sense of the resource, but it does not distinguish this from `apply_style_preset` or `apply_country_settings`, which share the same naming pattern.

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

Usage Guidelines2/5

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

The only guidance is that it is equivalent to apply_template; there is no explicit when-to-use, no condition under which an agent should pick this over apply_template (or when it would be preferred for aliasing), and no prerequisites stated. An agent reading this cannot tell why two names exist for the same operation.

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