Skip to main content
Glama

PokerAgile

add_stories

Append story titles to the room's list, for instance the sprint's stories read from your user's tracker. Returns how many were added, how many were refused and why, and the room state; refused when the host locked the room.

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

Input Schema

NameRequiredDescriptionDefault
roomYesthe room address or id
seatYesthe token join_room returned
storiesYesstory titles in the order to estimate them, one per item, 200 characters at most each

Output Schema

NameRequiredDescriptionDefault
whyYeswhy some were refused or shortened, empty when none was
addedYeshow many stories joined the list
stateYes
storyYesthe title of the story on the table
refusedYeshow many did not

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. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that this is an additive mutation, that results are partially applied (some added, some refused), the reason for refusal (host locked the room), and that room state is returned. Return-format details beyond this are left to the output schema.

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?

Front-loaded with the action and scope, then the outcomes, then the failure condition. It's a single dense sentence with some run-on feel in the trailing clauses, but nothing is wasted.

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?

Covers the prerequisite token, the mutation semantics, partial success, and the lock refusal — enough for an agent to call it correctly. Return-value explanation is partly redundant given the output schema, but that's a minor inefficiency rather than a gap.

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 three parameters are already documented, including that stories are ordered and capped at 200 characters. The description adds little beyond re-using the seat-as-join_room-token and ordering concepts already in the schema, so baseline 3 applies.

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 and resource: 'Append story titles to the room's list'. An agent can tell this adds stories rather than reading or voting on them. It doesn't explicitly name a sibling tool to contrast with, so it stops short of 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?

Gives a concrete usage example ('the sprint's stories read from your user's tracker') and implies a prerequisite via the seat token from join_room. However, it never states when NOT to use it or which sibling to reach for instead (e.g., get_estimates to read the list rather than append).

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.