Skip to main content
Glama

Lokand Restaurant MCP

Make menu only

make_menu_only
Destructive

Turn the site into a single menu page (the menu becomes the home page, every other page is disabled). Use when the owner wants "just the menu". 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>"
    },
    "name": "make_menu_only"
  }
}

Input Schema

NameRequiredDescriptionDefault
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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. The description adds the critical extra context annotations cannot: what gets affected (all other pages are disabled, not deleted) and that the change is revertible via revert_last_site_change. It doesn't address what a repeated call does, which idempotentHint=false leaves ambiguous.

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?

Two tight sentences with the state change front-loaded, followed by the usage trigger and the revert path. No filler or restated title.

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 single-parameter destructive mutation with no output schema, the description covers the blast radius and reversibility, which are the things an agent most needs. The remaining gap is the undocumented business_id parameter, which is left entirely to the schema.

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?

One parameter with 0% schema description coverage, and the description never mentions business_id at all. With low coverage the description is expected to compensate, but it adds no meaning about scoping, format, or which business's site is affected.

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?

A specific verb and resource plus the exact resulting state: the menu becomes the home page and every other page is disabled. The parenthetical makes the outcome unmistakable, so an agent knows precisely what the tool produces rather than guessing from the name.

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?

It gives a clear use condition ('when the owner wants 'just the menu'') and names the escape hatch, revert_last_site_change. It stops short of stating when NOT to use it, e.g. how this differs from create_full_menu or create_menu, but the trigger condition is explicit.

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