Skip to main content
Glama

sixta-connect

Digest a slow query log (SIXTA)

sixta_analyze_workload
Read-onlyIdempotent

Find your worst queries by TOTAL time — no connection needed. Paste a MySQL slow query log or a PostgreSQL pg_stat_statements export and get a ranked top-N: each query shape with calls, total/mean time, and (slow log) the rows-examined-to-sent ratio, fingerprinted so thousands of log lines collapse into a few classes. Flags the dominant query, N+1 patterns, and full-scan ratios, reports how concentrated the load is (what share of total time the top shapes own), and hands the worst offenders to sixta_analyze_query. Call this whenever the user shares a slow query log or pg_stat_statements export — even a long one — or asks which queries are slowest: summing time across thousands of log lines is arithmetic a model cannot do reliably by eye. Input is analyzed in memory and never stored.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
logYesA MySQL slow query log slice, or a pg_stat_statements export (tabular or \G), pasted or uploaded
engineNoDatabase engine: postgresql or mysql. Optional — auto-detected from the format.
versionNoEngine 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
NameRequiredDescriptionDefault
engineNoEngine the analysis targeted, when known.
reportYesThe full human-readable SIXTA report (markdown).
findingsNoNamed findings as structured data, when the tool produces them.
finding_countNoNumber of findings/issues identified.
overall_severityNoHighest severity across findings (Critical/High/Medium/Low/Info).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Description adds behavioral context beyond annotations: 'Input is analyzed in memory and never stored.' It details fingerprinting, flagging patterns, and concentration reporting. No contradiction with annotations (all read-only/idempotent).

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 front-loaded with purpose, but slightly verbose. Every sentence adds value, though minor redundancy could be trimmed. Still effective.

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 complexity (log parsing, ranking, flags), description covers inputs, outputs, behavior, data handling, and integration with sibling tools. Output schema exists and is not needed in description.

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% with descriptions; description adds value by explaining auto-detection of engine and version assumption, which goes beyond schema. Baseline 3, incremented for this 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's purpose: finding worst queries by total time from a slow query log or pg_stat_statements export. It distinguishes from siblings by mentioning handoff to sixta_analyze_query, and the verb 'analyze' is implied through 'find your worst 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 call: 'whenever the user shares a slow query log...or asks which queries are slowest.' It contrasts with manual arithmetic and hints at alternatives via sibling connection.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources