Skip to main content
Glama

PokerAgile

get_room

Read-only

Read a room: the deck (cards), the round, the title of the story on the table (story), the story list, who voted, and the results once a person has revealed the votes.

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": "get_room"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomYesthe room address or id

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=false, so the safety profile is covered. The description adds a genuinely useful behavioral nuance beyond that: results are only present 'once a person has revealed the votes', telling the agent the payload is state-dependent and may be partial.

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?

A single front-loaded sentence with no filler; the parenthetical glosses on 'cards' and 'story' aid comprehension. The trailing enumeration is dense but each item earns its place by telling the agent what to expect back.

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?

An output schema exists, so return values need not be spelled out, yet the description still previews them, which is helpful for a read tool. Nothing critical is missing for a one-parameter read, though a note on error behavior for invalid or unjoined rooms would round it out.

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?

Only one parameter (room) with 100% schema description coverage, so the schema already explains it as 'the room address or id'. The description adds nothing about the identifier format or how to obtain it, which is the baseline-3 outcome when the schema does the work.

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?

States a specific verb (Read) and resource (room), then enumerates exactly what is returned: deck/cards, round, story title, story list, voters, and results. That enumeration distinguishes it from siblings like join_room, vote, and add_stories, though no sibling is named explicitly.

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 way to inspect current room state before acting. There is no explicit when-to-use or when-not-to-use guidance, and no mention of alternatives such as get_estimates for results.

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.