Skip to main content
Glama

PokerAgile

join_room

Join a planning poker room as a participant marked as an AI. Returns the seat token and the room state.

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

Input Schema

NameRequiredDescriptionDefault
nameYesthe name shown to the team, e.g. Claude
roomYesthe room address shared by the team, or its id

Output Schema

NameRequiredDescriptionDefault
seatYesthe token to pass to vote, get_room and leave_room
stateYes

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. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the caller is registered as an AI participant and that a seat token plus room state are returned, but it omits whether joining is idempotent, whether the name must be unique, whether a seat is consumed, and what errors occur for an invalid room.

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?

Two short sentences, front-loaded with the action and followed by the return contract. Every clause carries information and nothing is padded.

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 simple two-parameter join tool with an output schema covering return values, the description is nearly sufficient. The remaining gap is failure and repeat-join behavior, which matters because the seat token presumably gates later calls.

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 description coverage is 100%, so both parameters (name, room) are already documented in the schema, including the 'Claude' example and the room address-or-id flexibility. The description adds no meaning beyond that, so the baseline of 3 applies.

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 gives a specific verb and resource ('Join a planning poker room') plus a distinguishing qualifier ('as a participant marked as an AI'), which separates it cleanly from siblings like get_room, leave_room, and vote without needing to name them.

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 only implied: an agent can infer this is the entry point before voting or adding stories, but the description never states when to use it versus get_room, nor what to do if already joined or if the room does not exist. No prerequisites or exclusions are given.

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.