Skip to main content
Glama

ArchGuard MCP

check_migration_safety

Audit PostgreSQL/MySQL/SQLite DDL migrations for production table locks and rolling-deploy breaks, generating a 3-phase Expand-Contract plan.

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": {
      "sql": "<sql>"
    },
    "name": "check_migration_safety"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYes
dialectNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses the output shape (3-phase Expand-Contract plan) and the failure modes it checks for, but says nothing about whether it connects to a live database or performs static parsing, whether it is read-only, or how large an input it accepts.

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 no filler; every clause carries information (engine scope, failure modes, output form).

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 tool with no output schema and no annotations, the description covers purpose and output shape but leaves the input contract underspecified. An agent can pick the tool confidently yet may pass the wrong form of SQL.

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

Parameters2/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, and it largely does not. The dialect list merely restates the enum, while the required 'sql' parameter is left ambiguous — single statement versus a multi-statement migration file, and whether non-DDL statements are tolerated, are unaddressed.

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?

The description names a specific verb (audit), a specific resource (DDL migrations), the supported engines (PostgreSQL/MySQL/SQLite), and the deliverable (a 3-phase Expand-Contract plan). It is clearly distinct from simulation and capacity siblings. It stops short of routing against the similarly named audit_code_snippet, so it is not a full 5.

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?

The phrase 'for production table locks and rolling-deploy breaks' implies the context in which to use it (pre-deploy review of a schema change), but there is no explicit when-to-use/when-not, no prerequisites, and no named alternative such as audit_code_snippet for general code review. Usage is inferable but not stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.