Skip to main content
Glama

PokerAgile

Server Details

Planning poker rooms an AI assistant can join and vote in, its card hidden until the team reveals.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
florianmousseau/pokeragile
GitHub Stars
1
Server Listing
pokeragile
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation4/5

Most tools target a distinct action (add, join, leave, vote, report, read). get_room and get_estimates overlap somewhat since both read the room/story list, but descriptions clarify that get_room is the full room snapshot while get_estimates focuses on kept estimates.

Naming Consistency4/5

Six of seven tools follow a clear verb_noun pattern (add_stories, get_estimates, get_room, join_room, leave_room, report_actual). Only 'vote' deviates as a bare verb, a minor inconsistency in an otherwise predictable scheme.

Tool Count5/5

Seven tools is well-scoped for a planning poker workflow. Each tool earns its place covering session entry/exit, story setup, voting, reading state, and reporting actuals.

Completeness4/5

The core lifecycle (join, add stories, vote, estimate, report actuals, leave) is covered. Some gaps exist, such as exposing a reveal-votes action and room creation/story removal, though these may be host-side UI functions the agent can work around.

Available Tools

7 tools
add_storiesAInspect

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.

Inputs: room (required), seat (required), stories (required). Returns: why, added, state, story, +1 more

get_estimatesA
Read-only
Inspect

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.

Inputs: room (required). Returns: stories, markdown

get_roomA
Read-only
Inspect

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.

Inputs: room (required). Returns: state, story

join_roomAInspect

Join a planning poker room as a participant marked as an AI. Returns the seat token and the room state.

Inputs: name (required), room (required). Returns: seat, state

leave_roomBInspect

Leave the room and give up the seat.

Inputs: room (required), seat (required). Returns: state, story

report_actualAInspect

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.

Inputs: room (required), seat (required), added (required), files (required), +4 more. Returns: stories, markdown

voteAInspect

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.

Inputs: card (required), room (required), seat (required), reason. Returns: state, story

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.