polyplan-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initA | Initialize PolyPlan in this project — creates .plans/ and .polyplan/ directories |
| round_1B | Start Round 1 — create an independent plan for this model/CLI (no other models seen) |
| round_1_contextA | Get the Round 1 prompt — call this first, then generate your plan, then call round_1 to save |
| round_2A | Start Round 2 — peer-review all Round 1 plans and write a revised master plan (requires ≥2 Round 1 plans) |
| round_2_contextA | Get the Round 2 prompt with all other models' Round 1 plans injected — call this before generating your Round 2 plan |
| final_planA | Start Final round — synthesize ALL Round 1 + Round 2 plans into one implementable plan (requires ≥1 Round 2 plan) |
| final_plan_contextA | Get the Final round prompt with ALL Round 1 + Round 2 plans injected — call this before generating the final plan |
| show_statusB | Show full session state — which models completed each round, open questions, and conflicts |
| clear_plansA | Delete plan files — target 'all', 'round1', 'round2', or 'final'. Must set confirm=true. |
| show_conflictsB | Show all points where models disagreed in Round 1 — technology choices, approach, and assumption conflicts |
| show_questionsA | Show all open questions raised by any model in Round 1, and whether other models answered them |
| show_diffB | Show what changed for a specific model between their Round 1 and Round 2 plans |
| show_agreeA | Show what ALL models agreed on independently in Round 1 — highest-confidence decisions |
| show_summaryA | One-paragraph summary of each model's plan — quick overview of all positions |
| export_plansA | Bundle the entire .plans/ session into one readable markdown file for sharing or archiving |
| show_historyB | Full audit log — which model, which CLI tool, which round, what time, what action |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 16 tools
Each tool has a clearly distinct purpose, covering specific actions like initialization, round management, context retrieval, and status queries. No two tools overlap in functionality, and descriptions make their roles unambiguous.
Tool names mostly follow predictable patterns: verbs for actions (clear, export, init), 'show_' for queries, and 'round_' nouns for round commands. The 'context' suffix for context tools and 'round_1' vs 'round_1_context' is consistent, though a few names (e.g., 'final_plan') mix noun phrases with actions.
16 tools is well-scoped for a planning session orchestrator covering init, two rounds, final synthesis, and full state queries. Each tool earns its place with no redundancy.
The tool set fully covers the planning lifecycle: initialization, round creation with context, final plan synthesis, status display, conflict/agreement analysis, history, and export. No obvious gaps like per-model plan deletion or editing are missing for the stated purpose.