Skip to main content
Glama
Sign In
Secure Git MCP

Secure Git MCP

by IvanAbramovichWork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

git_status

Read-onlyIdempotent

Shows the permitted working tree status for a repository, using the configured repository when no path is given and applying project policy restrictions.

Instructions

Show permitted working tree status. Omit repo_path to use the configured repository. Results and operations are restricted according to project policy.

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_pathNoOptional repository root. Omit to use the server's fixed repository. An explicit path must identify that same repository.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.10.19

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered. The description adds a policy-restriction note ("Results and operations are restricted according to project policy"), which hints that output may be filtered, but it never specifies what policy means or what gets hidden.

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?

Three short front-loaded sentences with no filler, and the default-behavior rule appears immediately after the purpose statement. Slightly repetitive with the schema's repo_path wording but not wasteful.

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

Completeness4/5

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

For a single-optional-parameter, read-only tool with an annotation-covered safety profile, this is nearly sufficient. The one remaining gap is that without an output schema, the description never says what the status report contains (branch, staged vs unstaged entries), though that is largely conventional for git status.

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 coverage is 100% and the schema itself explains that an explicit repo_path must identify the server's fixed repository. The description only restates the omit-default behavior, adding nothing beyond what the schema already provides, so the baseline of 3 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?

States a specific verb and resource ("Show ... working tree status"), which an agent can distinguish from diff/log siblings that inspect content rather than summary state. The word "permitted" adds a policy qualifier that is not explained, slightly clouding the core purpose.

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?

It gives a concrete rule for the repo_path parameter (omit to use the configured repository), but says nothing about when to prefer git_status over git_diff, git_diff_staged, or git_log, which are the realistic alternatives for inspecting working tree state.

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

Deploy Server

Other Tools