Inspect the active Git branch to review topology, uncommitted changes, upstream divergence, and recent commits, helping AI agents assess repository state before acting.
Inspects current Git branch topology, uncommitted file counts, upstream divergence, and recent commit history.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden; 'Inspects' signals a read-only operation and the facet list tells the agent what data surfaces. However it says nothing about prerequisites (must the working directory be a Git repo?), failure behavior outside a repo, cost/latency of walking commit history, or how much history 'recent' means.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single dense sentence with no filler; the core action leads and the four returned facets follow as a compact list. Nothing could be cut without losing information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description usefully names the return categories, which is the key omission risk for a zero-param tool. What remains uncovered is environmental scope (does it need a repo path or specific checkout, how much commit history, behavior when not in a Git repo), which keeps it short of a 5.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the baseline is 4 — there is nothing for the description to disambiguate and no schema-documented inputs to compensate for. The description correctly implies a parameterless snapshot of the current branch context.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Uses a specific verb ('Inspects') with a specific resource ('current Git branch') and enumerates exactly what facets it covers: topology, uncommitted file counts, upstream divergence, and recent commit history. That resource scope is unmistakably distinct from the siblings (smart_diff, scan_secrets, detect_conflicts, estimate_context_cost), so an agent can route without opening a schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The enumerated facets imply when the tool is useful (whenever you need a branch-state snapshot), but there is no explicit 'use this when…' guidance, no exclusions, and no mention of the sibling tools or when one of them would be the better choice. Usage is inferable but not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.