Skip to main content
Glama

PokerAgile

leave_room

Leave the room and give up the seat.

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": {
      "room": "<room>",
      "seat": "<seat>"
    },
    "name": "leave_room"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomYesthe room address or id
seatYesthe token join_room returned

Output Schema

NameRequiredDescriptionDefault
stateYes
storyYesthe title of the story on the table, empty when the room has no list

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / state / properties / references
      Added value: +{
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "card": {
      +        "type": "string"
      +      },
      +      "title": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "card",
      +      "title"
      +    ],
      +    "type": "object"
      +  },
      +  "type": [
      +    "null",
      +    "array"
      +  ]
      +}
    • addedOutput schema / properties / state / properties / stories / items / properties / actual
      Added value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "added": {
      +      "description": "lines added",
      +      "type": "integer"
      +    },
      +    "files": {
      +      "description": "files touched",
      +      "type": "integer"
      +    },
      +    "minutes": {
      +      "description": "working time in minutes, 0 when unknown",
      +      "type": "integer"
      +    },
      +    "removed": {
      +      "description": "lines removed",
      +      "type": "integer"
      +    },
      +    "tests": {
      +      "description": "tests added",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "files",
      +    "added",
      +    "removed",
      +    "tests",
      +    "minutes"
      +  ],
      +  "type": [
      +    "null",
      +    "object"
      +  ]
      +}
    • addedOutput schema / properties / state / properties / stories / items / properties / looksLike
      Added value: +{
      +  "type": "string"
      +}
  2. Changed2 schema fields changed
    • addedOutput schema / properties / story
      Added value: +{
      +  "description": "the title of the story on the table, empty when the room has no list",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "state"
      -]New value: +[
      +  "story",
      +  "state"
      +]
  3. First observed

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It mentions that the seat is given up, which hints at token invalidation, but it does not describe permissions, reversibility, error behavior, or whether the room persists after leaving.

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?

The definition is a single front-loaded sentence with zero wasted wording. It states the action and the key effect in immediate succession.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter operation with full schema coverage and an output schema, the description covers the action and immediate effect. It is still missing usage context relative to join_room and behavioral details such as failure modes, which leaves the definition minimally adequate rather than complete.

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?

The schema has 100% description coverage for both required parameters, so parameter meaning is already well documented. The description adds no syntax or format details beyond what the schema provides, making the baseline score appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ('Leave the room') and clarifies the side effect ('give up the seat'). It does not explicitly contrast with siblings such as join_room or get_room, but the core purpose is unambiguous.

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: this is the exit action after joining a room. However, the description gives no explicit when-to-use conditions, prerequisites, or alternatives, leaving the agent to infer context from the tool name and siblings.

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.