Skip to main content
Glama

Lokand Restaurant MCP

Update item

update_item
Destructive

Update a menu item's fields (name, description, price, availability, category, sort order). Only provided fields change. Setting is_available=false takes a dish off the public site (86 it).

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": {
      "item_id": "<item_id>"
    },
    "name": "update_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
priceNo
item_idYes
sort_orderNo
variationsNoReplaces the item's whole variation list. Variations keep their identity by name, so re-sending the list to change one price is safe. Pass null to drop variations entirely — send `price` alongside it, otherwise the item keeps its old 'from' price.
category_idNo
descriptionNo
dietary_infoNoAllergen and dietary labels shown to diners. `allergens` uses the 14 standard codes (gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame, sulphites, lupin, molluscs); `contains` flags alcohol, pork or tobacco; `suitableFor` carries positive claims (vegetarian, vegan, halal, ...); `caloriesKcal` and `portionGrams` are per portion. Optional `declaredAt` (epoch-ms) records that a dish was reviewed, which sharpens check_compliance — a dish with no allergens and no declaredAt is indistinguishable from one nobody has looked at yet.
is_availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true; the description adds genuine value beyond them by stating that unspecified fields are preserved and that is_available=false removes the item from the public site ("86 it"). Minor tension with idempotentHint=false, since merge-style updates are naturally idempotent, but the description is not directly contradicting the annotation.

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 (mutable fields, merge semantics, availability consequence), with the most important behavioral fact front-loaded. No filler.

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

Completeness3/5

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

For a destructive, nine-parameter mutation with no output schema, the description covers partial-update behavior and the visibility effect of is_available but omits the variation-list replacement semantics and dietary metadata. An agent can call it correctly for simple field edits but would be under-informed on the complex parameters.

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 description coverage is only 22%, so the description carries real weight, yet it only lists the six simple fields and says nothing about variations or dietary_info — the two most consequential parameters. Those two happen to have verbose schema descriptions the agent can fall back on, which keeps this from scoring lower, but the description itself adds little parameter meaning.

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?

Names a specific verb and resource ("Update a menu item's fields") and enumerates the mutable fields, which distinguishes it cleanly from add_item and delete_item. It stops short of explicitly naming a sibling or scope boundary, so it is clear but not maximally differentiating.

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

Usage Guidelines3/5

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

"Only provided fields change" establishes partial-update semantics and "Setting is_available=false takes a dish off the public site" gives one concrete usage consequence. There is no guidance on when to use this versus add_item/delete_item, nor on the variations workflow (replace whole list vs. create separate items), which the schema itself frames as a use-this-instead decision.

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