Skip to main content
Glama

Lokand Restaurant MCP

Create full menu

create_full_menu
Destructive

Create a COMPLETE menu (sections + items) in one call — prefer this over separate create_menu/add_category/add_item calls. With replace=true, existing menus are deactivated so this becomes the business's live menu (their data is kept, just hidden).

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>",
      "menu": "<menu>"
    },
    "name": "create_full_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
menuYes
replaceNoDeactivate the business's other menus in the same step
business_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, so the description's key contribution is clarifying that replace=true deactivates other menus while keeping their data ("their data is kept, just hidden") — exactly the context needed to judge the destructive flag. It doesn't address permissions, failure modes, or whether deactivated menus can be reactivated, so it stops short of full transparency.

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 sentences, both earning their place: the first establishes scope and routing, the second disambiguates the destructive flag. The parenthetical and the replace clause are front-loaded where the reader needs them.

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 nested three-parameter create tool with a destructive flag and no output schema, the description covers the two things structured data can't: why to choose it over siblings and what replace actually does to existing data. Cardinality limits and per-item fields are already in the schema, so the remaining gaps are minor.

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?

Schema coverage is only 33%, but the description compensates for the highest-risk parameter by explaining replace=true's effect beyond the schema's terse "Deactivate the business's other menus in the same step." It says nothing about business_id or the menu object's structure, leaving the caller to rely on the (admittedly detailed) nested schema.

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 specific verb and resource ("Create a COMPLETE menu (sections + items)") and immediately distinguishes itself from the sibling primitives create_menu/add_category/add_item. An agent can tell exactly what this tool produces versus the granular alternatives.

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?

Explicitly says to prefer this over separate create_menu/add_category/add_item calls, naming the alternatives and the condition that selects this one. It also scopes the replace=true variant as the way to make the menu live, which is the main decision point for the caller.

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