Skip to main content
Glama
Sign In
ForgeMCP

ForgeMCP

by hardened-steel
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

git_restore

Destructive

Restore selected working files from the Git index or a specified commit to undo unwanted changes or recover file contents.

Instructions

Restore selected working files from the index or an explicit commit.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "paths": "<paths>"
    },
    "name": "git_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathsYes
sourceNo

Output Schema

NameRequiredDescriptionDefault
errorNo
changesYes
updatesNo
conflictsYes
operationYes
head_afterYes
head_beforeYes
process_idsYes
synchronization_errorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating operation. The description adds the useful detail that files can come from the index or a commit, but it does not state that unstaged changes may be discarded or clarify the default behavior when no source is provided.

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

Conciseness5/5

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

The definition is a single, front-loaded sentence with no redundant wording. It communicates the core action and source options efficiently.

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?

For a destructive Git operation with an output schema, the definition is only partially complete. It should more explicitly explain the default source behavior and the consequences of restoring over uncommitted changes, given that the annotations already flag the operation as destructive.

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 0%, so the description must carry the burden of explaining parameters. It clarifies 'paths' as selected working files and 'source' as either the index or an explicit commit, but it does not explain the null default for source or the accepted commit format.

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?

The description gives a specific verb and resource ('Restore selected working files') and names two source modes: the index or an explicit commit. It is clear what the tool does, though it does not explicitly distinguish itself from nearby siblings such as git_unstage or git_revert.

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?

There is no explicit guidance on when to use this versus git_unstage, git_revert, or git_stash, nor any warning about when restoring from the index is preferable to restoring from a commit. The two source modes are mentioned, but the conditions for choosing between them are left to inference.

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