Intelligent Database DBA & Schema Migration Guardrail MCP Server

dry_run_migration

Executes DDL migrations in an isolated SAVEPOINT, evaluates risk, and always rolls back to return guardrail warnings without persisting schema changes.

Instructions

Executes a DDL migration inside an isolated SAVEPOINT, evaluates risks, then ALWAYS rolls back. Returns risk assessment and guardrail warnings.

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": {
      "migrationSql": "<migrationSql>"
    },
    "name": "dry_run_migration"
  }
}

Input Schema

Name	Required	Description	Default
`migrationSql`	Yes	The DDL SQL statement to dry-run (will be fully rolled back)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations exist, so the description does the heavy lifting and does it well: it discloses isolation via SAVEPOINT, guaranteed rollback, risk evaluation, and the shape of the output (risk assessment plus guardrail warnings). It stops short of stating required database privileges, supported SQL dialects, or the caveat that some engines auto-commit DDL and may not honor the rollback.

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?

Two tight sentences with no filler; the operation, the isolation/rollback guarantee, and the return value are all front-loaded in reading order.

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?

For a one-parameter, no-output-schema tool this covers the essentials: what runs, that it is always reverted, and what comes back. Minor gaps are the granularity of the risk assessment and any privilege or dialect requirements, which an agent would otherwise have to discover by calling.

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% and the single parameter is already documented as the DDL statement that will be fully rolled back. The description's only added signal is the DDL-only constraint (migrations/statement types), which is marginal, so this sits at the schema-driven baseline.

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 and resource ("Executes a DDL migration") plus the two distinctive behaviors (isolated SAVEPOINT, ALWAYS rolls back) and the return payload. That clearly separates it from the inspection/seed/index siblings without needing to name them.

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 only implied: an agent can infer this is the safe way to validate DDL before applying it, and "ALWAYS rolls back" signals non-committal trial. There is no explicit trigger (e.g. "call before running a real migration"), no stated preconditions, and no named alternative for actually applying the change.

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

Deploy Server