sixta-connect

Explain a database error code (SIXTA)

sixta_explain_error

Read-onlyIdempotent

Decode a database error and get the fix and the next step — no connection needed. Paste a MySQL error number (1213, 1062, 1452, 1205…) or a PostgreSQL SQLSTATE (40P01, 23505, 53300…), optionally with the failing statement, and get the proximate cause, the concrete fix, and — when it helps — the SIXTA tool and artifact to go deeper (e.g. a deadlock → paste SHOW ENGINE INNODB STATUS for sixta_explain_deadlock). Use when the user pastes a DB error code or message. Input is analyzed in memory and never stored.

Input Schema

TableJSON Schema

Name	Required	Description
`error`	Yes	The error code or message (e.g. 'ERROR 1213', 'SQLSTATE 40P01', or the full error text)
`engine`	No	Database engine: postgresql or mysql. Optional — disambiguates a numeric code.
`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

A4.9/5.0

Behavior5/5

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

Annotations already indicate readOnly and idempotent. Description adds 'no connection needed' and 'Input is analyzed in memory and never stored,' enhancing transparency about side effects and privacy.

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?

Concise single paragraph with clear structure: purpose, examples, usage, privacy note. Every sentence adds value.

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?

For a simple tool, covers input, output (cause, fix, deeper tool suggestions), privacy, and sibling differentiation. No missing context given the complexity.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description adds value by giving concrete examples (1213, 1062, 40P01) and explaining optional parameters (engine, version) with usage context.

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?

The description clearly states the tool decodes database errors and provides fixes, with specific examples for MySQL and PostgreSQL. It distinguishes from siblings by mentioning a deeper tool (sixta_explain_deadlock) for specific cases.

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 says 'Use when the user pastes a DB error code or message.' Provides alternative guidance (e.g., deadlock → use sixta_explain_deadlock).

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?