Skip to main content
Glama

Add tables

add_table

Restaurants and bars: adds a table (or several identical ones) with its seats. Online bookings get the smallest free table that fits the party. Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>",
      "name": "<name>",
      "seats": "<seats>"
    },
    "name": "add_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYese.g. "Table" or "Terrace". Numbered automatically when count > 1.
countNoHow many identical tables, default 1 (max 40).
seatsYes1-30.
addressYesThe venue’s address name, the "name" in name.bookare.app.
access_keyYesThe venue’s access key.
from_party_ofNoSmallest party it is given to online, default 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=false), the description discloses that multiple identical tables can be created in one call and that online bookings are allocated the smallest free table that fits the party — meaningful side-effect context for a scheduling system. It does not warn about duplicate creation on retry despite idempotentHint=false, which is the main remaining gap.

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 short sentences, each carrying distinct information: domain scope, bulk/allocation behavior, and the venue addressing constraint. Nothing is repeated from the schema field descriptions and nothing is wasted.

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 mutation tool with full schema documentation and safety annotations, the description covers who it is for, how targets are addressed, and the allocation behavior. It stops short of covering name-uniqueness/error behavior and the effect of `count` on numbering, which the schema covers only partially ("Numbered automatically when count > 1").

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 100%, so the baseline is 3, but the description adds relational meaning: "several identical ones" explains `count` as duplicate creation and the booking-allocation sentence gives the real purpose of `from_party_of`. That is genuine value over the per-field schema text.

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 domain qualifier ("Restaurants and bars") and a specific verb+resource ("adds a table (or several identical ones) with its seats"). No sibling tool touches tables, and the bulk nuance is stated up front, so an agent can identify the operation immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Use is implied by the domain scoping (restaurants and bars) and the constraint that it acts on one venue via address and access key. There is no explicit when-to-use/when-not guidance, no alternatives mentioned, and no note on what to do if a table name already exists.

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