sixta-connect

Explain an EXPLAIN plan (SIXTA)

sixta_explain_plan

Read-onlyIdempotent

Turn raw EXPLAIN output into a plain-language diagnosis — no query needed. Paste PostgreSQL EXPLAIN / EXPLAIN ANALYZE (text or JSON) or MySQL EXPLAIN (tabular, \G, FORMAT=JSON, FORMAT=TREE) and get: what the planner is doing step by step, where the cost concentrates, named risk findings (full scans, spilling sorts, nested-loop blowups, row misestimates) with index suggestions, and what to look at next. Use when the user pastes EXPLAIN output or asks 'can you read this plan'. Input is analyzed in memory and never stored.

Input Schema

TableJSON Schema

Name	Required	Description
`plan`	Yes	Raw EXPLAIN output, pasted verbatim (any supported format)
`engine`	Yes	Database engine: postgresql or mysql
`version`	No	Engine version, e.g. '16' (PostgreSQL major) or '8.0.35' (MySQL). Omit for a modern default; some verdicts are version-dependent and the assumption is stated in the result.

Output Schema

TableJSON Schema

Name	Required	Description
`engine`	No	Engine the analysis targeted, when known.
`report`	Yes	The full human-readable SIXTA report (markdown).
`findings`	No	Named findings as structured data, when the tool produces them.
`finding_count`	No	Number of findings/issues identified.
`overall_severity`	No	Highest severity across findings (Critical/High/Medium/Low/Info).

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 28, 2026

TDQS

A5/5.0

Behavior5/5

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

Discloses that input is analyzed in memory and never stored, adding safety context beyond annotations (readOnlyHint, destructiveHint). Also describes output nature (risk findings, index suggestions) without contradicting annotations.

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?

Single focused paragraph with front-loaded purpose, each sentence adds distinct value (input formats, output, usage trigger, privacy). No redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers input formats, output content, privacy guarantee, and appropriate usage context. Output schema exists (referenced) so return structure is already documented, making description complete.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and description enriches by listing exact supported formats for each engine, clarifying version optionality, and explaining how each parameter affects the analysis.

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?

Description clearly states verb+resource: 'turn raw EXPLAIN output into a plain-language diagnosis'. It specifies supported formats and output components, distinguishing it from siblings like sixta_analyze_query which analyzes queries.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'Use when the user pastes EXPLAIN output or asks can you read this plan'. Implicitly excludes query analysis, guiding toward appropriate sibling tools.

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

All sixta-connect tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?