Skip to main content
Glama
Sign In
Secure Git MCP

Secure Git MCP

by IvanAbramovichWork
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

git_reset

DestructiveIdempotent

Unstage the full staged set only if policy permits; omit repo_path to target the configured repository.

Instructions

Unstage only when the complete staged set is permitted. 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_reset"
  }
}

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

C2.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description adds that operations are restricted by project policy, which is useful context, but it does not specify what exactly is unstaged, whether working-tree changes are affected, or what happens if policy blocks the operation.

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

Conciseness3/5

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

The description is short, but it is front-loaded with a confusing conditional rather than a clear purpose statement. The second sentence largely repeats the schema, and the third is a vague policy note.

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

Completeness2/5

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

For a destructive git tool with a close sibling (git_unstage), the description omits critical context: the difference between reset and unstage, what 'complete staged set' means, and what is actually changed. With no output schema and only annotations covering basic safety hints, more explanation is needed.

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 schema already explains that repo_path is optional and must identify the configured repository. The description repeats the omission behavior without adding format or semantic detail beyond the schema, so the baseline of 3 applies.

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

Purpose3/5

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

The description includes the verb 'Unstage' and scope 'complete staged set', but the phrase 'only when the complete staged set is permitted' is a cryptic condition rather than a clear definition. It does not explain how this differs from the sibling git_unstage or what git reset actually resets.

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

Usage Guidelines2/5

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

It gives a vague condition ('only when the complete staged set is permitted') but no explicit guidance on when to use this tool versus git_unstage or other reset alternatives. The repo_path omission note is usage detail, not selection guidance.

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