Skip to main content
Glama

Remove guest from table

unseat-guest
DestructiveIdempotent

Takes an invitation off a table of the seating plan: everyone of the party seated there goes back to the guests still to seat. Also how to clear a seat of someone who is no longer coming. The guest stays on the guest list.

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": "unseat-guest"
  }
}

Input Schema

NameRequiredDescriptionDefault
guest_idYesThe invitation, from get-seating or search-guests.
table_idYesThe table they sit at, shown as [table 3] by get-seating.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. Beyond that, the description discloses real consequences the annotations cannot: the entire party is unseated from the table, they move back to 'guests still to seat,' and the guest record survives. It doesn't state whether the seat itself remains available afterwards.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core effect is front-loaded in the first clause, which is good. But the second sentence is a sentence fragment ('Also how to clear a seat…') that reads as awkward phrasing rather than a clean instruction, costing structure points despite the short overall length.

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 two-parameter mutation with no output schema, this covers what an agent most needs: the unit of removal is the party, the side effect is returning them to the unseated pool, and the guest record persists. The only notable gap is what happens to the vacated seat and whether a table can be left empty.

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

Parameters3/5

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

Schema coverage is 100%, so guest_id and table_id are already fully documented, including where to obtain them. The description adds a conceptual point — that guest_id refers to an entire invitation/party, not just one person — but no format or lookup detail beyond the schema.

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 names a specific operation on a specific resource — taking an invitation off a table in the seating plan — and states the resulting state change (the whole party returns to the unseated pool). It also distinguishes itself from delete-guest by explicitly saying 'The guest stays on the guest list.'

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?

Usage is implied rather than stated: the second sentence offers a scenario ('clear a seat of someone who is no longer coming') that indicates when to reach for this tool. However, it never names seat-guest or delete-guest as the alternatives, nor does it state when not to use it.

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