ChatGPT2LocalBridge

Overview Schema Source Related Servers Discussions Admin

Git Checkpoint

git.checkpoint

Read-only

Save the current Git commit as a checkpoint before making risky edits, allowing you to restore the working tree to this state if needed.

Instructions

Return the current HEAD commit. Use this before a risky edit so git.revert can restore the working tree to this 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": {
      "projectPath": "<projectPath>"
    },
    "name": "git.checkpoint"
  }
}

Input Schema

Name	Required	Description	Default
`projectPath`	Yes

Output Schema

Name	Required	Description	Default
`checkpoint`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 19, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds that it returns HEAD commit, but does not detail any other behavioral traits like response format or edge cases. With annotations covering safety, a 3 is appropriate.

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?

Two sentences, no repetition, front-loaded with the action. Every word serves a purpose.

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 simple read-only tool with a single parameter and an output schema (not shown but indicated), the description covers the core action and usage pattern. The missing parameter guidance prevents a perfect score.

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

Parameters1/5

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

The sole parameter 'projectPath' has no description in the schema (coverage 0%), and the description does not mention it at all, leaving the agent to infer its necessity and format without guidance.

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?

Clearly states 'Return the current HEAD commit' as the primary action. Distinguishes from sibling tools like git.revert and git.status by focusing on capturing a point for potential reversion.

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?

Explicitly advises using 'before a risky edit' and references git.revert as the recovery mechanism, providing clear context for when to invoke this tool.

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