Skip to main content
Glama

check_rollback_conflicts

Detects overlapping file changes before rolling back a feature, comparing target files against other feature modifications to identify rollback conflicts.

Instructions

Check for potential conflicts before rolling back a feature. Compares files modified by the target feature against files modified by other features to detect overlapping changes that would be affected by rollback.

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": {
      "projectDir": "<projectDir>",
      "featureId": "<featureId>"
    },
    "name": "check_rollback_conflicts"
  }
}

Input Schema

NameRequiredDescriptionDefault
featureIdYesID of the feature to check rollback conflicts for
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description must carry behavioral disclosure. It implies a non-mutating analysis and explains the comparison logic, but says nothing about permissions, performance on large change sets, or what a conflict result looks like, so an agent cannot fully predict 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.

Conciseness4/5

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

Two sentences, front-loaded with the action and followed by the mechanism. No filler or repetition, though the second sentence could have been used to add return-value or constraint detail rather than pure mechanism.

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 simple two-parameter check tool this covers purpose well, but no output schema exists and the description never indicates whether the result is a boolean, a conflict list, or per-file overlap detail. That missing return-shape information is a real gap for an agent deciding how to react to the result.

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 both parameters (featureId, projectDir) are documented in the schema, so the baseline of 3 applies. The description adds no further meaning such as format, validation rules, or path constraints beyond what the schema already states.

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 ('check for potential conflicts') and explains the mechanism: comparing the target feature's modified files against files modified by other features. This clearly distinguishes it from a mutation tool like rollback_feature, though it stops short of naming that sibling explicitly.

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

Usage Guidelines4/5

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

The phrase 'before rolling back a feature' gives a clear temporal trigger that an agent can act on. There is no explicit when-not guidance or named alternative, so it falls short of the top band, but the intended workflow position is unambiguous.

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