Skip to main content
Glama

Git Status

git_status

Display the working tree status of a Git repository to identify staged, unstaged, and untracked changes before committing.

Instructions

Show the working tree status (git status).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "git_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_pathNoPath to the git repository..

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations supplied, the description must carry the behavioral load. "Show" signals a read-only inspection and "working tree" scopes the report to staged/unstaged/untracked changes, which is genuinely useful context. However, it never explicitly states that the call has no side effects, and offers no note on behavior in a non-repo path or on large repositories.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence, front-loaded with the operative verb and resource. The "(git status)" gloss is mildly redundant with the tool name and title, but it costs almost nothing and aids command recognition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (one optional parameter) and an output schema exists, so return values need not be explained. Still, with zero annotations, the description is thinner than ideal for its complexity because it omits the read-only/side-effect guarantee an agent would want before calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single optional repo_path parameter already documents itself ("Path to the git repository.", default "."). The description adds no further meaning about that parameter, so the baseline of 3 for a fully documented schema applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Show the working tree status" states a specific verb (show) and resource (working tree status), and the parenthetical "(git status)" anchors it to the canonical command. It is clearly distinguishable from siblings like git_diff and git_log by the fact it reports state rather than diffs or history. It stops short of naming those siblings, so it is not a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent infers this is the tool to call when it wants a snapshot of uncommitted/staged/untracked state. There is no explicit when-to-use versus git_diff or git_log, and no prerequisites or exclusions are stated. Common knowledge of git status does most of the routing work here.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.