Inspect a repository's working tree at a glance: return its short change list and summarized diff stats versus HEAD, optionally targeting a given directory.
git status (short) plus diff stat against HEAD.
| Name | Required | Description | Default |
|---|---|---|---|
| path | No | Repository directory (default: default workspace) |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, and non-destructive, so the safety profile is covered by structured data. The description adds useful behavioral content in that it reveals output composition (short status format plus a diffstat against HEAD), but says nothing about untracked files, staging areas, or what happens in a non-repo directory.
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 short sentence with zero waste and the key output qualifiers ('short', 'against HEAD') front-loaded. It is arguably under-specified rather than over-long, but it is efficiently structured.
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 must convey what is returned; it does partially by naming status-short plus diffstat. However, it omits whether untracked/ignored files appear, staged vs unstaged separation, and failure behavior outside a repository, leaving meaningful gaps for a tool an agent will use to decide next steps.
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?
There is only one optional parameter and its schema description ('Repository directory (default: default workspace)') already carries 100% coverage of its meaning. The description adds no syntax or default-behavior detail beyond the schema, so the baseline 3 applies.
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?
The description names a specific git operation and its scope ('status (short) plus diff stat against HEAD'), so an agent knows it reports working-tree state rather than commits or diffs alone. It does not explicitly distinguish itself from siblings like git_diff or git_log, which keeps it out of 5 territory.
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?
There is no when-to-use guidance, no prerequisites, and no mention of the obvious alternative git_diff even though the description itself includes diff-stat output. The agent must infer selection context on its own.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.