Skip to main content
Glama

git_status

Read-only

Check a mirror repo's current branch, commits ahead or behind the remote, and every changed file. Run it before committing or pulling to see what will be included.

Instructions

Show the git status of a place's mirror repo: current branch, commits ahead or behind the remote, and each changed file. Read-only. Run it before git_commit to see what will be committed, or before git_pull to make sure nothing is uncommitted. For line-level changes use git_diff.

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
placeNoTarget place (PlaceId or project name) whose mirror repo to use. Defaults to the bound/sole connected place.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / place / description
      Previous value: -"Target place (PlaceId or project name); defaults to the bound/sole place"New value: +"Target place (PlaceId or project name) whose mirror repo to use. Defaults to the bound/sole connected place."
  2. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces that with "Read-only" while adding useful substance: the operation targets a mirror repo and reports branch, divergence, and per-file state. It stops short of noting limits such as whether untracked files are included or how large change sets are presented, so it is strong but not fully descriptive beyond the annotations.

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?

The definition is front-loaded with purpose, then behavior, then workflow guidance, and the final sentence redirects to git_diff, so every part is functional. The standalone "Read-only." fragment largely restates the annotation and is the only mildly redundant element.

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

Completeness5/5

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

There is no output schema, and the description compensates by naming the fields the agent will see (branch, ahead/behind, changed files). Combined with the preconditions for git_commit and git_pull, an agent has everything needed to call this correctly and interpret the result.

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?

With a single parameter and 100% schema description coverage, the schema already explains the PlaceId-or-name target and the default to the bound/sole place. The description never mentions the place argument, so it adds nothing on this dimension beyond the structured field, which is the expected baseline here.

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

Purpose5/5

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

States a specific verb and resource ("Show the git status of a place's mirror repo") and enumerates exactly what is returned: current branch, ahead/behind counts, and each changed file. It explicitly separates itself from git_diff by scoping itself to summary status rather than line-level changes.

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

Usage Guidelines5/5

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

Gives concrete when-to-use guidance tied to siblings: run before git_commit to preview what will be committed, and before git_pull to confirm nothing is uncommitted. It also names the alternative (git_diff) for the case this tool does not cover, so the routing decision is fully determined.

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