rollout-playbook-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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_playbooksA | Search across all rollout/deployment playbooks for a keyword or phrase and return matching sections |
| generate_rollout_planB | Generate a tailored deployment rollout plan checklist based on project type, team size, and risk level |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| assess_deployment_risk | Generate a structured risk assessment for a proposed deployment |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| rollout-checklist | Rollout Checklist — enterprise deployment playbook |
| risk-assessment-framework | Risk Assessment Framework — enterprise deployment playbook |
| stakeholder-raci-template | Stakeholder RACI Template — enterprise deployment playbook |
| migration-cutover-plan | Migration Cutover Plan — enterprise deployment playbook |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one searches existing playbooks, the other generates new plans. No overlap or confusion possible.
Both tools follow a consistent verb_noun pattern: search_playbooks and generate_rollout_plan. Naming is clear and predictable.
With only 2 tools, the server feels very thin for a 'rollout-playbook' domain. A typical set would include at least listing, retrieving, creating, and updating playbooks.
The domain of rollout playbooks is missing fundamental operations like create, read, update, delete, and execute playbooks. Only search and generate are present, leaving significant gaps.