Skip to main content
Glama

PokerAgile

get_estimates

Read-only

Read the story list with the estimate the team kept for each, as data and as a Markdown table. Call it before you vote, to place the story among the estimates already kept, and when the session is over, to write the estimates back to the tracker.

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_estimates"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomYesthe room address or id

Output Schema

NameRequiredDescriptionDefault
storiesYes
markdownYesthe same list as a Markdown table

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / stories / items / properties / actual
      Added value: +{
      +  "additionalProperties": false,
      +  "description": "what the story cost once delivered, when someone reported it",
      +  "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 / stories / items / properties / looksLike
      Added value: +{
      +  "description": "the card this measure is closest to among the other measured stories, empty while there are too few",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.2/5.0
Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a safe read, and the description's claim to "read" is consistent with that. Beyond the annotations it supplies workflow framing (pre-vote and end-of-session), but it discloses nothing about access requirements, rate limits, or why idempotentHint is false on what looks like a pure read.

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?

A single sentence with no filler, front-loaded with what is read and its output shape, followed by the two usage moments. Every clause carries information an agent would act on.

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 one-parameter read tool with a published output schema and full schema coverage, the definition supplies everything needed to call it correctly. The only weak spot is the closing clause about writing estimates back to the tracker, which describes an end-of-session write purpose inside a read-only tool and could briefly muddle what the call itself does.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is only one parameter, room, and the schema documents it at 100% coverage as the room address or id. With a single fully described parameter, the baseline is 4 and the description adds nothing that needs to compensate.

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 opening clause gives a specific verb and resource: read the story list together with the estimate kept for each, and it states the return shape (data plus a Markdown table). That is concrete enough to separate it from siblings like vote or report_actual without inspecting any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives two explicit moments to call the tool: before voting, to position a story against kept estimates, and at session end, to write estimates back to the tracker. There is no when-not guidance and no sibling is named as an alternative, which keeps it short of a full 5.

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.