Skip to main content
Glama

Lokand Restaurant MCP

Update menu

update_menu
Destructive

Rename a menu, change its description, or switch it on/off on the public site (is_active). Only provided fields change. Menu ids come from get_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": {
      "menu_id": "<menu_id>"
    },
    "name": "update_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
menu_idYes
is_activeNoWhether the menu is live on the public site
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false; the description adds genuine context by disclosing that is_active toggles visibility on the public site and that unspecified fields are left alone. It does not explain why the call is destructive (no mention of irreversibility, live-site impact, or permissions), so it adds value beyond the annotations without fully covering their implications.

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 short sentences, each carrying distinct information: what changes, the partial-update rule, and the ID source. Nothing is redundant and the core action is front-loaded.

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 four-parameter mutation with no output schema, the definition covers every parameter, the partial-update contract, and the ID prerequisite. Remaining gaps are minor: no mention of what a successful response looks like or which permission is required.

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

Parameters4/5

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

Schema description coverage is only 25%, so the description compensates well by naming all three editable fields (name, description, is_active) and explaining where menu_id originates. It adds meaning beyond the bare property names, though it does not state constraints such as length limits or bounds/collision errors.

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

Purpose4/5

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

The description uses a concrete verb set (rename, change description, switch on/off) tied to a single resource (menu), and scopes the mutation to three named fields. It is clearly distinguishable from create_menu/delete_menu, though it does not name a sibling explicitly.

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 real prerequisite by stating 'Menu ids come from get_status', which tells the agent how to obtain the required argument before calling. It also clarifies partial-update behavior ('Only provided fields change'), but offers no exclusions or alternative tool for related operations.

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