Skip to main content
Glama
Sign In
sql-query-mcp

sql-query-mcp

by andyWang1688
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

explain_query

Run EXPLAIN on read-only SELECT or CTE queries to analyze query execution plans. Optionally include ANALYZE for actual execution times.

Instructions

Run EXPLAIN on a read-only SELECT or CTE query.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "connection_id": "<connection_id>",
      "sql": "<sql>"
    },
    "name": "explain_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYes
analyzeNo
connection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0
  2. Removedv0.1.2
  3. First observedv0.1.3

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It states the tool is read-only and runs EXPLAIN, which is generally non-destructive. However, it does not detail permissions, side effects, or output format. This is minimally adequate but lacks depth.

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?

The description is a single, concise sentence with no redundant information. It directly communicates the tool's function.

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

Completeness1/5

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

Given no output schema, no annotations, and three parameters with zero description coverage, the description is extremely incomplete. It fails to provide essential details for agent usage, such as parameter meanings, output structure, or behavioral nuances.

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

Parameters1/5

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

Schema description coverage is 0%, and the tool description adds no parameter details. The three parameters (sql, analyze, connection_id) are not explained at all. Without additional context in the description, the agent cannot understand parameter semantics.

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 runs EXPLAIN on read-only SELECT or CTE queries. This distinguishes it from siblings like run_select (which executes the query) and describe_table (which describes tables). The verb 'Run EXPLAIN' and resource 'SELECT or CTE query' are specific.

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

Usage Guidelines4/5

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

The description specifies the queries are 'read-only SELECT or CTE', implying it should be used for analyzing query plans and not for DML queries. It clearly indicates the context but does not explicitly mention when not to use or list alternatives among siblings.

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

Deploy Server

Other Tools