Skip to main content
Glama

Add products

add_products

Use when the venue owner asks to add new products to their own menu. Put each product in an existing category (category_id from get_my_menu) or in a new one (new_category_name; reused if a category with that name already exists). Keep names and prices exactly as the owner says; never invent descriptions or allergens. Up to 50 products per call. Two steps: call first without confirm to get the preview (nothing is saved), show it to the owner, and only after they agree call again with confirm: true. New texts are translated automatically. 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": {
      "items": "<items>"
    },
    "name": "add_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
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?

Annotations only declare readOnlyHint=false and destructiveHint=false; the description goes well beyond by explaining that the unconfirmed call saves nothing, that confirmation is a separate deliberate call, that new texts are auto-translated, and that categories with a matching name are reused rather than duplicated. It also constrains content generation ("never invent descriptions or allergens") and notes the account-connection requirement.

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?

Usage condition and categorisation choice are front-loaded, and each sentence carries operational weight. It is dense — six clauses covering flow, limits, translation, auth, and tone — so an agent must parse carefully, but there is no filler.

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 mutating, non-idempotent tool with no output schema, the description covers everything needed to call it safely: the preview/confirm gate, batch ceiling, category resolution rules, auth precondition, and translation behaviour. Nothing material is left for the agent to guess.

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 schema already documents price currency, station default, and category_id. The description still adds meaning the schema does not: new_category_name is reused if a category of that name exists, and confirm distinguishes a non-persisting preview from a save gated on owner approval.

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 opens with a specific verb and resource scoped to the owner's own menu ("add new products to their own menu"), which cleanly separates it from update_products and hide_products by implication of the verb. It also names get_my_menu as the source of category_id, giving the agent an unambiguous entry point.

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?

It states when to use it (owner asks to add products), how to choose between the two categorisation paths (category_id vs new_category_name), and the mandatory two-step protocol: preview first without confirm, then confirm: true only after the owner agrees. Preconditions (PRENOTO account connection) and a hard limit (50 per call) are also spelled out.

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