Skip to main content
Glama

PokerAgile

report_actual

Report what a story the team estimated cost once delivered: files touched, lines added and removed, tests added, working time. Numbers only. Returns the list with each measure and the card it looks like; refused for a story with no kept estimate, and 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>",
      "story": "<story>",
      "files": "<files>",
      "added": "<added>",
      "removed": "<removed>"
    },
    "name": "report_actual"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomYesthe room address or id
seatYesthe token join_room returned
addedYeslines added
filesYesfiles touched
storyYesthe position of the story in get_estimates, from 1
testsNotests added
minutesNoworking time in minutes, when known
removedYeslines removed

Output Schema

NameRequiredDescriptionDefault
storiesYes
markdownYesthe same list as a Markdown table

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 burden and does disclose two concrete failure modes: refusal for a story with no kept estimate, and refusal when the host has locked the room. It also states "Numbers only" and describes the return shape. It does not say whether re-reporting overwrites prior figures or whether the record is permanent, which is a meaningful gap for a write operation.

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?

The description is short and front-loads purpose before return behavior and refusals. The mid-text fragment "Numbers only." and the cryptic "the card it looks like" clause cost some clarity without adding length.

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 an 8-parameter write tool with an output schema and no annotations, the definition covers purpose, the shape of the result, and the two documented refusal paths. Remaining gaps concern persistence and repeat-call semantics rather than anything the schema or output schema already answers.

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 all eight parameters are already documented in the schema, including the mapping of story position to get_estimates and the optional minutes/tests fields. The description adds no format or constraint detail beyond what the schema supplies, so the baseline of 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?

The description names the specific action (report delivered actuals for an estimated story) and enumerates the measures: files touched, lines added/removed, tests added, working time. It is distinguishable from siblings like get_estimates or vote. The phrasing "what a story the team estimated cost once delivered" is grammatically strained and the clause "the card it looks like" is opaque, which blunts otherwise clear intent.

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?

"once delivered" implies the timing (after the work is done) and the refusal for a story with no kept estimate hints that get_estimates must come first. However, no sibling is named as an alternative, and there is no explicit when-not-to-use guidance beyond the refusal conditions.

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.