Skip to main content
Glama

Change products

update_products
Idempotent

Use when the venue owner asks to change products on their own menu: price, name, description, ingredients, allergens, availability (sold out / back) or featured. Identify products by product_id from get_my_menu; if several products match what the owner said (for example two with the same name), ask which one. Up to 50 products per call. Two steps: call first without confirm to get the before/after (nothing is saved), show it to the owner, and only after they agree call again with the same changes and confirm: true. Allergens: only the 14 EU codes and only when the owner states them; never guess. Changed texts are translated automatically. Every change can be undone with undo_change. Requires the owner to connect their PRENOTO account. Reply in the owner's language.

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": {
      "changes": "<changes>"
    },
    "name": "update_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYes
confirmNofalse or omitted: preview only. true: save, only after the owner agreed to the preview.
venue_idNoOptional. Only needed when the account manages several venues (see list_my_venues).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond annotations that mark this as a non-read-only, non-destructive, idempotent mutation, the description discloses the critical two-step preview/confirm workflow, that nothing is saved on the first call, the 50-product limit, automatic translation, undo support, and the PRENOTO account requirement. These are substantive behavioral details an agent needs before invoking the tool.

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

Conciseness4/5

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

The description is dense but front-loaded with the usage condition and follows a logical order: identification, limits, preview/confirm workflow, allergen rules, translation, undo, and prerequisites. It contains no filler, though it is longer than a minimal description because the workflow genuinely has several constraints.

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

Completeness5/5

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

For a mutation tool with no output schema, the description is complete: it explains the preview/save behavior, how to identify products, how to resolve ambiguity, the call limit, allergen restrictions, translation behavior, undo support, and account prerequisites. An agent has enough information to invoke it correctly and safely.

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 coverage is 67%, and the description adds meaningful semantics beyond field definitions: product_id must come from get_my_menu, confirm is only for saving after the owner approves the preview, and allergens are replaced and must be limited to owner-stated EU codes. It does not explicitly explain venue_id, but the schema covers that parameter sufficiently.

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?

The description states a specific verb and resource: changing products on the venue owner's own menu, with editable fields such as price, name, description, ingredients, allergens, availability, and featured status. It clearly distinguishes this from reading the menu by requiring product_id from get_my_menu, and it separates itself from sibling tools like add_products and hide_products.

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?

The description explicitly says when to use the tool: when the venue owner asks to change products on their own menu. It provides concrete operational guidance: identify products via get_my_menu, ask which product if several match, preview first without confirm, save only after owner agreement, restrict allergens to stated EU codes, and use undo_change to reverse changes.

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