Inspect table structure
Establish which schemas, tables, columns and data types are in scope before comparing or moving data. Guide-derived workflow; compare with the current six-tool MCP surface.
This is an operational workflow, not an additional callable MCP tool. See the six current tools.
Operator question
What exactly exists in the source and target environments?
The guide's operational SQL example joins sys.tables, sys.schemas, sys.columns and sys.types to inventory table structure.
Context a call would need
- Source and target environment identifiers
- Database and table scope
- Access permitted for metadata inspection
Evidence to return
- Schema and table identity
- Column names, order and data types
- Collection time and environment provenance
Safety and availability
The current get_table_schema tool supports this for one selected table. It calls the SQL Cockpit REST API; API permissions and nested connection fields must be checked against the deployment.