Intelligent Database DBA & Schema Migration Guardrail MCP Server

inspect_table_schema

Retrieve detailed table schema information—column types, nullability, primary and foreign keys, and index coverage—to validate structure before database changes.

Instructions

Returns detailed schema info for a table: column types, nullability, primary keys, foreign keys, and index coverage metrics.

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": {
      "tableName": "<tableName>"
    },
    "name": "inspect_table_schema"
  }
}

Input Schema

Name	Required	Description	Default
`tableName`	Yes	The name of the table to inspect

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 13, 2026

TDQS

A3.6/5.0

Behavior3/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. It does usefully disclose the exact shape of what is returned, but says nothing about side effects being absent, permissions required, behavior on non-existent tables or views, or cost of the inspection.

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 zero filler; the enumerated return fields earn their place by telling the agent what it will get back in the absence of an output schema.

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 no output schema, the description correctly uses its space to spell out the return payload, which is the main thing an agent needs for a one-parameter read tool. Minor gaps remain around error conditions and permission requirements.

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?

Only one parameter (tableName) with 100% schema description coverage, so the schema already explains it fully. The description adds no qualification such as schema-qualification format (e.g. schema.table) or case sensitivity, so it does not exceed the baseline for a fully documented single parameter.

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 ('Returns') and resource ('detailed schema info for a table') and enumerates exactly what is included: column types, nullability, primary keys, foreign keys, index coverage metrics. An agent can tell this apart from explain_query_plan or suggest_optimal_indexes by the returned content, though the description never names a sibling to contrast against.

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 by the returned content — an agent infers it should call this when it needs column/key/index metadata. There is no explicit statement of when to prefer this over explain_query_plan or suggest_optimal_indexes, and no prerequisites or exclusions are given.

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

Deploy Server