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

sql-query-mcp

by andyWang1688
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

get_query

Check the status of an asynchronous query and retrieve paginated results upon completion.

Instructions

Get asynchronous query status and paginated results when complete.

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": {
      "query_id": "<query_id>"
    },
    "name": "get_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
query_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description bears full burden. It mentions async behavior and pagination but fails to disclose what happens if the query is still running, the format of status responses, or how to handle errors. Lacks details on polling behavior.

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 wasted words. It efficiently communicates the core functionality.

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

Completeness2/5

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

The tool is moderately complex (async, paginated, status check) and has no output schema. The description is too brief to cover necessary context like how to poll for status, interpret results, or handle partial results. Leaves significant gaps.

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

Parameters2/5

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

Schema description coverage is 0%, so description must compensate. It adds minimal meaning by mentioning 'paginated results' which hints at limit/offset, but does not explain query_id or the behavior of limit/offset defaults. Leaves parameter semantics largely unexplained.

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 retrieves asynchronous query status and paginated results when complete, using specific verb and resource. It distinguishes from siblings like start_query and run_select by focusing on the retrieval of results.

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

Usage Guidelines3/5

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

The description implies the tool should be used after a query is complete, but provides no explicit when-to-use or when-not-to-use guidance. It does not name alternatives like cancel_query or explain_query.

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