git_paw/mcp/tools/mod.rs
1//! MCP tool definitions, one file per category (design D2).
2//!
3//! Each category file adds an `impl GitPawMcpServer` block carrying its
4//! `#[tool]` methods and a named `#[tool_router(...)]`; [`crate::mcp::server`]
5//! merges the per-category routers into the server's combined router. Tool
6//! methods are thin: they parse parameters, call [`crate::mcp::query`], and
7//! wrap the result as MCP structured content. Per the degradation contract
8//! (design D4) most tools return successful empty/null payloads when their
9//! data source is absent; only genuine misconfiguration surfaces as an
10//! [`rmcp::ErrorData`].
11
12pub mod coordination;
13pub mod docs;
14pub mod git;
15pub mod governance;
16pub mod project;
17pub mod session;
18pub mod source;