Skip to main content
Glama

Create a digital QR menu

create_menu_preview

Use when the user asks to create a digital or QR menu for a restaurant, bar, café or hotel. Convert the venue's existing menu (photo, PDF or text shared by the user) into this JSON. Keep dish names and prices exactly as written, keep categories in menu order and never invent dishes, descriptions or allergens; put any doubt in notes. Creates a private preview link where the venue owner reviews, edits and activates the menu. The menu is translated automatically into English, Italian, Spanish, French, German and Portuguese. Side effect: every call creates a new preview, so retrying creates another link. Images are not accepted; the owner adds photos after activating. Reply to the user in their own 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": {
      "business": "<business>",
      "categories": "<categories>"
    },
    "name": "create_menu_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoDoubts while reading the menu (illegible prices, unclear items). The owner sees them as warnings.
businessYes
categoriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations: it states the call produces a private preview link that the owner must review, edit and activate, that every call creates a new preview so retries spawn extra links (reinforcing idempotentHint=false), that the menu is auto-translated into six languages, and that images are rejected until activation. These are exactly the operational consequences an agent needs before invoking a non-idempotent mutation.

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?

Trigger, data-fidelity rules, side effects and constraints are packed into a short block with the most decision-relevant content first. The six-language list slightly duplicates the defaultLanguage schema description, and the closing 'Reply to the user in their own language' is a stylistic instruction rather than tool behavior, but nothing is padded.

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 non-idempotent creation tool with a large nested schema and no output schema, the description covers outcome (preview link), post-call workflow (owner edits and activates), side effects and input limitations. Remaining gaps are minor: no mention of authentication or of what the preview link response actually contains beyond 'a private preview link'.

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?

With only 33% schema description coverage across a deeply nested object, the description compensates by defining content rules that map to parameters: dish names and prices verbatim, categories in menu order, allergens never invented, doubts routed into notes. Business-level fields such as currency, businessType and defaultLanguage are left to the schema, which does document them, so the gap is small rather than harmful.

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 names a concrete verb and resource ('create a digital or QR menu'), supported by the conversion framing ('Convert the venue's existing menu (photo, PDF or text) into this JSON') and the venue types it serves. It does not differentiate from the siblings (about_prenoto_menu, get_menu_format), so an agent must infer that those are info/reference tools rather than creation paths.

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?

The opening clause gives an explicit trigger ('Use when the user asks to create a digital or QR menu for a restaurant, bar, café or hotel') and the tool adds real constraints: images are not accepted, retries create duplicate previews, and the reply must match the user's language. It stops short of naming when to prefer the sibling tools (e.g. fetching the format via get_menu_format first).

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