Release Readiness Triage MCP

analyze_rollback_readiness

Scans repository database migrations to classify each change as rollback-safe or destructive, returning blocking migrations and deployment strategy for rollback readiness assessment.

Instructions

Scans a repository for versioned database migration files (Flyway V*.sql, Prisma migration.sql, Liquibase XML/YAML) and classifies each operation as additive (rollback safe) or destructive (forward-fix only). Returns rollback_eligible, a list of blocking_migrations with file and line, and deployment_strategy. Use before recommending deployment to determine whether a rollback is safe after go-live.

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": {
      "repo_path": "<repo_path>"
    },
    "name": "analyze_rollback_readiness"
  }
}

Input Schema

Name	Required	Description	Default
`repo_path`	Yes	Absolute path to the repository root to scan for migration files

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the full burden. It describes the scanning, classification, and return fields (rollback_eligible, blocking_migrations, deployment_strategy), implying a read-only operation. It does not mention edge cases or permissions, but the core behavior is transparently disclosed.

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?

The description is a single compact sentence that front-loads the action and includes concrete file patterns, outputs, and usage context. Every phrase adds value with no wasted words.

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?

With one parameter, no output schema, and no annotations, the description provides a solid picture of what the tool does and returns. It covers purpose, examples, outputs, and usage timing. It could elaborate on classification details or error cases, but the core is sufficiently complete for an agent to invoke it correctly.

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 coverage is 100% (repo_path described as 'Absolute path to the repository root to scan for migration files'). The description adds no new semantics beyond the schema, so the baseline of 3 applies.

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?

The description clearly states a specific action (scans a repository) and resource (versioned database migration files), and specifies the classification (additive vs destructive). It also names output fields, distinguishing it from sibling tools that focus on test failure analysis.

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?

Explicitly states when to use ('Use before recommending deployment') and the goal (determine rollback safety after go-live). It does not mention when not to use, but the clear context is sufficient given the unrelated sibling tools.

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

Deploy Server