F
licenseA
qualityD
maintenanceEnables AI assistants to manage tasks across multiple projects with structured Markdown files, supporting creation, updates, completion, and organization with metadata and dependencies.
7
-
Poker Task Management MCP
by Hirao-Y
Related Servers
Alternatives to Poker Task Management MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to create, manage, and break down tasks into subtasks with priorities, and track progress through a hierarchical task list.11 npm13GPL 3.0
- FlicenseAqualityDmaintenanceEnables comprehensive task management with groups, custom statuses, and task relationships, designed for AI assistants to manage tasks during conversations.17-
- FlicenseAqualityDmaintenanceEnables AI assistants to manage tasks through a comprehensive interface with 8 tools for creating, updating, searching, and tracking tasks with priorities, categories, and due dates. Features persistent file-based storage, advanced filtering, and task statistics for complete task management workflow.8-
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage a local-first Kanban board with Azure DevOps-style workflow rules, including task creation, status updates, subtask breakdown, full-text search, daily summaries, and next-task suggestions.-
- AlicenseBqualityCmaintenanceTask planning and tracking for AI agents with project-based organization and Obsidian-compatible markdown storage.137 npmMIT
TDQS
B3/5.0
Scored across 26 tools
Disambiguation5/5
Every tool has a clearly distinct purpose targeting specific resources (Body, BuildupFactor, Detector, Source, Transform, Zone, Unit) and actions (analyze, apply, change, delete, execute, get, propose, update, validate). There is no ambiguity or overlap between tools, as each handles a unique operation on a specific entity in the radiation shielding calculation domain.
Naming Consistency5/5
All tools follow a consistent verb_noun pattern with the prefix 'poker_' (e.g., poker_deleteBody, poker_proposeDetector, poker_updateUnit). The naming is uniform across all 26 tools, using snake_case and clear action-resource combinations, making it highly predictable and readable.
Tool Count2/5
With 26 tools, the count is too high for typical MCP server scope, which usually benefits from 3-15 tools. While the domain (radiation shielding calculation) is complex, the tool set feels heavy and could overwhelm agents, suggesting potential over-fragmentation of operations.
Completeness5/5
The tool set provides complete CRUD/lifecycle coverage for the domain, including propose (create), get, update, and delete operations for all key entities (Body, BuildupFactor, Detector, Source, Transform, Zone, Unit), plus analysis, validation, and execution tools. There are no obvious gaps, ensuring agents can handle full workflows without dead ends.
Maintenance
ActivityActive
ResponsivenessNo issues