commit-discipline-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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plan_taskA | Create an ordered 2-4 stage commit plan from a clean Git worktree. |
| commit_stageA | Test, size-check, stage, and commit only the next declared plan stage. |
| task_statusA | Read the active plan, completed commits, and next stage. |
| finish_taskA | Mark a complete, clean task plan as finished. |
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 4 tools
Each tool has a unique, non-overlapping role: plan creation, stage execution, status inspection, and task completion. No ambiguity in purpose.
All tool names follow the consistent verb_noun pattern (plan_task, commit_stage, task_status, finish_task), making the API predictable.
4 tools provide a focused, well-scoped workflow for commit discipline without unnecessary bloat or missing essentials.
The toolset covers the full lifecycle: create plan, execute stages, check status, and finish. No obvious gaps in the workflow.