Skip to main content
Glama
Sign In
upgrade-pilot-mcp

upgrade-pilot-mcp

by kdinisv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Restore git checkpoint

restore_checkpoint

Restore a project to a previously saved checkpoint using a specific label. Revert changes and reset state to a known stable point, enabling safe undo and rollback during dependency upgrades.

Instructions

Hard-reset to a previously created checkpoint tag.

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": {
      "label": "<label>"
    },
    "name": "restore_checkpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
labelYes
rootPathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations provided, the description must carry full behavioral transparency weight. 'Hard-reset' implies a destructive, irreversible operation (losing uncommitted changes), but the description does not state this explicitly, nor does it mention permissions or side effects. The agent cannot infer safety profile from this alone.

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?

One short sentence is efficient, but it omits critical information about the tool's behavior (see behavioral transparency). Conciseness is about being not verbose, not about being incomplete. The sentence earns its place but fails to convey enough.

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?

The tool is complex (destructive operation, multiple params, sibling ecosystem) with no annotations and no output schema. The description is not complete enough: it does not explain the effect on the working directory, whether it's reversible, what happens, or how rootPath relates to checkpoint. Significant gaps remain.

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% (no param descriptions in schema), so the description must compensate. It mentions 'label' is a checkpoint tag (which adds some meaning), but 'rootPath' is entirely undocumented. Baseline 3 would require full schema coverage; here, partial compensation plus one uncovered param yields a 3.

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 uses a specific verb ('Hard-reset') and clearly identifies the resource ('previously created checkpoint tag'). It distinguishes from sibling tools like 'create_checkpoint' (which creates, not resets) and 'list_checkpoints' (which lists). A 5 would require explicit mention of differentiation from siblings, but the action is still clear.

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

Usage Guidelines1/5

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

No usage context is provided, no when or when-not to use, no alternatives mentioned. Given that sibling tools include 'check_compatibility' and many other operations that might be prerequisites or safer alternatives, the description offers zero guidance, making this dimension critically weak.

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