Skip to main content
Glama

PokerAgile

vote

Vote one card of the room deck with a short reason, both hidden from the team until the reveal. An empty card withdraws the vote.

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

Input Schema

NameRequiredDescriptionDefault
cardYesone card of the room deck, or empty to withdraw the vote
roomYesthe room address or id
seatYesthe token join_room returned
reasonNowhy this card, in one or two sentences; shown to the team at the reveal

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.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses a non-obvious trait — the vote and reason stay hidden from the team until the reveal — but leaves out whether a second vote overwrites the first, whether the seat must be valid, and what failures look like.

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 with no filler, and the core action plus the withdrawal exception are both front-loaded. Every clause earns its place.

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 and the input schema is fully described, so the description only needs to convey intent and the hidden-until-reveal behavior, which it does. The remaining gap — repeated-vote semantics — is minor for a four-parameter tool.

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 all four parameters are already documented in the input schema, establishing a baseline of 3. The description only reinforces that 'card' may be empty to withdraw and implies the reason is also hidden, adding marginal meaning beyond the schema.

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 names a specific verb and resource ('Vote one card of the room deck') and adds a second mode ('An empty card withdraws the vote'), so the agent can tell what the tool does without opening the schema. It does not explicitly differentiate itself from siblings such as report_actual, so it stops short of a 5.

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: the agent can infer it applies to a joined room and that passing an empty card switches to withdrawal. There is no statement of when to prefer this over alternatives, no prerequisite (e.g. must have joined the room via join_room), and no note on whether re-voting replaces the previous vote.

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.