Expand description
MCP tool definitions, one file per category (design D2).
Each category file adds an impl GitPawMcpServer block carrying its
#[tool] methods and a named #[tool_router(...)]; crate::mcp::server
merges the per-category routers into the server’s combined router. Tool
methods are thin: they parse parameters, call crate::mcp::query, and
wrap the result as MCP structured content. Per the degradation contract
(design D4) most tools return successful empty/null payloads when their
data source is absent; only genuine misconfiguration surfaces as an
rmcp::ErrorData.
Modules§
- coordination
- Coordination tools:
get_intents,get_intent,get_conflicts. - docs
- Documentation tools:
get_readme,list_docs,get_doc. - git
- Git-context tools:
get_branches,get_recent_commits,get_diff. - governance
- Governance tools:
get_adrs,get_adr,get_test_strategy,get_security_checklist,get_dod,check_dod,get_constitution. - project
- Project-knowledge tools:
get_specs,get_spec,get_tasks,get_task,get_dependency_graph,get_skill. - session
- Session-state tools:
get_session_status,get_session_summary,get_learnings. - source
- Source-browsing tools:
list_files,read_file,search_code.