Skip to main content
Glama

Lokand Restaurant MCP

Export qr codes

export_qr_codes
Read-onlyIdempotent

Render the business's QR codes as a printable file and return a download URL. purpose: menu (one code to the menu site, repeated copies times), table_ordering (ONE CODE PER TABLE, each with its table name printed under it — needs tables, see create_tables) or link (its short links). format: home_pdf (A4/Letter sheets with cut guides, for a home printer; layout large=1, medium=4, small=12 per page), press_pdf (print shop: one code per page at size_mm wide, 3 mm bleed, trim box and crop marks, all vector) or svg_zip (one vector SVG per code, for a designer). Uses the saved design (get_qr_design) unless design overrides it for this file only.

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_id": "<business_id>",
      "purpose": "<purpose>"
    },
    "name": "export_qr_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
paperNohome_pdf: default a4
copiesNomenu/link: copies of each code; default fills one sheet
designNo
formatNoDefault home_pdf
layoutNohome_pdf: default medium
purposeYes
size_mmNopress_pdf/svg_zip: printed code width in mm; default 90
bleed_mmNopress_pdf: default 3
table_idsNotable_ordering: which tables; default all active ones
print_linkNoAlso return print_link: a short link to forward to a print shop, opening a download page with the press PDF + SVGs and their specs (expires in 60 days). Default true for press_pdf and svg_zip
business_idYes
shortlink_idsNolink: which short links (default all); menu: the short link to encode

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real behavioral context beyond that: it returns a download URL, press_pdf/svg_zip default print_link to true and that link expires in 60 days, and a `design` override applies to this file only rather than persisting. Rate limits and file naming are unmentioned, keeping it below a 5.

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 core action and return value are front-loaded in the first sentence, and each following clause maps to a decision the caller must make. It is dense with parentheticals and long sentences, which slightly hurts scanability, but no sentence is filler.

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 12-parameter tool with a nested design object and no output schema, the description covers the return value (download URL, print_link), the cross-tool dependencies (get_qr_design, create_tables), and the per-mode semantics of every consequential parameter. Remaining gaps are minor, such as what the returned file is named or how large exports are delivered.

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

Parameters5/5

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

With 75% schema coverage the baseline is 3, but the description goes well past the schema: it explains that `copies` repeats the menu/link code, that `layout` yields 1/4/12 codes per page, that `size_mm` is the printed code width with 3 mm bleed and trim marks for press_pdf, and that `shortlink_ids` means 'the short link to encode' for menu versus a filter for link. That is genuine semantic value, not restatement.

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?

Opens with a specific verb and resource: 'Render the business's QR codes as a printable file and return a download URL.' It then enumerates the three purpose modes (menu, table_ordering, link) with the distinct artifact each produces, so an agent can tell it apart from get_qr_design or create_tables without opening a schema.

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?

Guidance is explicit at two levels: purpose (menu = one code, table_ordering = one code per table and 'needs tables, see create_tables', link = its short links) and format (home_pdf for a home printer, press_pdf for a print shop, svg_zip for a designer). It also states the design-source rule: saved design from get_qr_design unless `design` overrides.

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