compose-bridge

Overview Schema Source Related Servers Discussions Admin

rollback_pattern

Reverts all file changes made by a specific replace_pattern call using its pattern_id, restoring files byte-for-byte when a pattern edit caused regressions.

Instructions

Rolls back ALL changes made by a specific replace_pattern call.

What it does: Requires pattern_id from the original replace_pattern response. All files are reverted byte-for-byte.
When to use: When a replace_pattern operation caused regressions and needs complete reversal.
When NOT to use: Cannot undo if files were modified externally. Use rollback_last for single-edit undo.
Side effects: Destructive rollback. Modifies all files touched by the pattern back to their prior state.
Parameters:
  - pattern_id: The exact pattern_id from the original replace_pattern response.
Returns:
  JSON string with list of reverted files and status.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pattern_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 19, 2026

TDQS

A4.6/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden, and it does well: it flags destructive rollback, byte-for-byte reversion, and the limitation that externally modified files cannot be undone. It omits details like permissions or whether the rollback itself is reversible, keeping it just short of a 5.

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?

Front-loaded with the action, then cleanly sectioned into use/not-use/side-effects. The 'Returns' line is somewhat redundant since an output schema exists, but the overall structure is tight and scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter destructive tool with no annotations, it covers purpose, routing, side effects, prerequisite parameter source, and error limits. With an output schema present, its return summary is a bonus rather than a gap.

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

Parameters4/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 compensate. It explains pattern_id as the exact pattern_id from the original replace_pattern response, which is more than the bare 'Pattern Id' title conveys, though no format example is given.

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?

States a specific verb (rolls back) and scope (ALL changes made by a specific replace_pattern call). Clearly differentiates itself from the sibling rollback_last, which it names explicitly.

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?

Explicit 'When to use' (replace_pattern caused regressions needing complete reversal) and 'When NOT to use' (files modified externally), plus a direct alternative (rollback_last for single-edit undo). All routing conditions are stated.

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