sixta-connect

Diagnose a database symptom (SIXTA)

sixta_diagnose

Read-only

SIXTA's deepest free analysis: bring a symptom ('p99 spiked after Tuesday's deploy', 'this endpoint times out') plus whatever artifacts exist — query, EXPLAIN output, table DDL, diagnostics excerpts — and get one coherent diagnosis: ranked hypotheses with the evidence for each, and next steps ordered by information gained. Runs SIXTA's deterministic analyzers across all artifacts, then a synthesis pass connects them. Use for vague or multi-artifact problems where no single tool fits; for a single query/plan/DDL artifact, prefer the specific tool. Anonymous use is limited to a couple of calls — do not call repeatedly. Input is analyzed in memory and never stored.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	No	Optional: the suspect SQL query
`engine`	Yes	Database engine: postgresql or mysql
`symptom`	Yes	The problem in the user's words — what changed, when, what it affects, and any cause they already suspect or setting they ask about (pass these through; SIXTA will address each lead)
`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.
`table_ddl`	No	Optional: CREATE TABLE / index DDL, or a proposed migration
`diagnostics`	No	Optional: pasted diagnostics the user ran themselves (pg_stat_statements excerpts, SHOW ENGINE INNODB STATUS, vacuum stats)
`explain_output`	No	Optional: EXPLAIN / EXPLAIN ANALYZE output (any format)

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.6/5.0

Behavior5/5

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

Annotations indicate read-only, non-destructive behavior. Description adds that input is analyzed in memory and never stored, and mentions rate limits. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is well-structured and informative, with key points front-loaded. Slightly verbose but all content earns its place.

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?

Given the complexity (7 params, output schema exists), the description covers inputs, usage, behavior, and limitations comprehensively.

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?

Schema coverage is 100%, so baseline is 3. The description adds some context (e.g., symptom description advises passing through user's leads), but does not significantly expand on schema details.

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's purpose: diagnosing a database symptom using multiple artifacts. It distinguishes from sibling tools by noting it is for vague or multi-artifact problems, while single-artifact tools should be preferred.

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: for vague or multi-artifact problems, and when not to use: for single artifacts, prefer specific tools. Also mentions anonymous usage limits.

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?