Skip to main content
Glama

Seat guest at table

seat-guest
Destructive

Seats an invitation at a table of the seating plan: everyone of the party without a seat yet, or the given number of seats to split a party over tables. A party that already sits at exactly one other table is moved; to move from one of several tables, pass from_table_id. Only invitations that said yes or have not answered get a seat. A table may go over capacity.

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": {
      "guest_id": "<guest_id>",
      "table_id": "<table_id>"
    },
    "name": "seat-guest"
  }
}

Input Schema

NameRequiredDescriptionDefault
seatsNoOnly part of the party, to split it over tables. Default: everyone without a seat yet.
guest_idYesThe invitation, from get-seating or search-guests.
table_idYesThe table to seat them at, shown as [table 3] by get-seating.
from_table_idNoMove the party's seats from this table instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare a destructive, non-read-only mutation; the description adds the substantive behaviors: it seats a whole party or a subset, it moves existing seats, it requires from_table_id when a party spans multiple tables, it filters on RSVP status, and it explicitly permits exceeding table capacity. Those are exactly the surprises an agent needs to know before calling.

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?

Three dense sentences, front-loaded with the core action and each sentence carrying distinct information (seating breadth, move semantics, RSVP filter, capacity rule). Minor grammatical awkwardness ('everyone of the party without a seat yet') slightly slows parsing but 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 four-parameter mutation with rich annotations and full schema coverage, the description covers eligibility, party expansion, and move behavior well. The only gap is that it says nothing about what the call returns (no output schema exists), though that is secondary for this tool.

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 baseline would be 3, but the description adds real meaning: it explains that seats defaults to 'everyone without a seat yet' and is used to split a party, and it clarifies that from_table_id selects the source table for a move. guest_id and table_id are only weakly elaborated in prose, but the schema already covers them.

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 definition opens with a specific verb and resource ('Seats an invitation at a table of the seating plan') and immediately narrows scope with party-level semantics ('everyone of the party without a seat yet, or the given number of seats'). This is clearly distinguishable from unseat-guest and add-seating-table without opening any 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?

It states the eligibility precondition ('Only invitations that said yes or have not answered get a seat') and explains when to supply from_table_id ('to move from one of several tables'). It doesn't explicitly name unseat-guest as the inverse operation, so routing is strong but not fully enumerated.

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