Skip to main content
Glama
Sign In
PC-Fixer MCP Server

PC-Fixer MCP Server

by toprakahmetaydogmus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pc_fixer_rollback

Roll back a previously applied healing transaction by transaction ID to restore modified files to their exact pre-fix state.

Instructions

Roll back a previously executed healing transaction using its unique transaction ID, restoring modified files to their exact pre-fix state.

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": {
      "transaction_id": "<transaction_id>"
    },
    "name": "pc_fixer_rollback"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoWorkspace root directory containing the transaction backup.
transaction_idYesThe transaction ID returned by pc_fixer_auto_heal (e.g. 'tx_12345_abcdef')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It does disclose the core mutation effect (files are restored to their exact pre-fix state), which is genuinely useful. It does not say whether the rollback is itself reversible, whether files created by the fix are removed, whether permissions are required, or how partial/failed rollbacks behave.

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?

A single front-loaded sentence with zero filler: the action, the identifier, and the outcome are all delivered immediately. Nothing is repeated or padded.

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 two-parameter mutation tool with no annotations and no output schema, the description covers the primary effect but leaves failure modes, output/confirmation behavior, and the role of the 'path' parameter unexplained. It is minimally adequate rather than complete.

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%, so both parameters are already documented, including the format example for transaction_id. The description only restates 'using its unique transaction ID' and never mentions the 'path' workspace-root parameter, adding nothing beyond the schema. Baseline 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: 'Roll back a previously executed healing transaction' and names the identifier used. The effect ('restoring modified files to their exact pre-fix state') makes the inverse relationship to pc_fixer_auto_heal inferable, though no sibling is named explicitly in the description itself.

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?

Usage is implied by 'previously executed healing transaction' — an agent can infer this is the undo path after a heal. However, there is no explicit when-not guidance, no mention of prerequisites (a transaction backup must still exist), and no statement about what to do if the transaction ID is unknown or expired.

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