Skip to main content
Glama

Lokand Restaurant MCP

Create tables

create_tables

Add tables in bulk — each gets its own permanent table-ordering QR code with its name printed under it. Either pass names (["Table 1","Terrace 2"]) or count with an optional prefix ("Table" → "Table 4", "Table 5", … continuing after the highest existing number). Names that already exist are skipped. Follow with export_qr_codes(purpose: table_ordering) to print them.

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>"
    },
    "name": "create_tables"
  }
}

Input Schema

NameRequiredDescriptionDefault
zoneNoArea, e.g. "Terrace"
countNoHow many numbered tables to add
namesNoExact table names
prefixNoName before the number; default "Table"
business_idYes
start_numberNoFirst number; default continues after existing ones

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say it is a non-destructive write with open-world effects. The description adds behavior the agent cannot get elsewhere: numbering continues after the highest existing number, prefix defaults to 'Table', existing names are silently skipped, and the created QR codes are permanent. The skip behavior is especially important given idempotentHint=false, since retries can yield partial results.

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 sentences, front-loaded with the outcome, then the two mutually exclusive calling modes, then the next step. Every clause carries operational information (examples, defaults, dedup rule, follow-up call) with no 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 6-parameter bulk mutation with no output schema, the definition covers the important ground: creation outcome, numbering rules, and duplicate handling. It leaves the return shape and whether skipped names are reported or silently ignored unstated.

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 83% schema coverage the baseline is 3, but the description goes further by showing concrete argument shapes ('Terrace 2', 'Table 4, Table 5, …') and clarifying that numbering resumes after existing tables. `zone` is only implied through an example name and `start_number` is not mentioned at all, so it is not exhaustive.

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?

States a specific verb and resource ('Add tables in bulk') and immediately explains the side effect: each table gets its own permanent table-ordering QR code with the name printed under it. That distinguishes it cleanly from list_tables (read) and export_qr_codes (printing) without needing to open 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 Guidelines4/5

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

Gives concrete mode-selection guidance (use `names` for exact labels, or `count` + `prefix` for auto-numbered tables) and names the explicit follow-on tool with its argument: export_qr_codes(purpose: table_ordering). It does not discuss when not to create tables or how this relates to list_tables, so it stops short of full alternative coverage.

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