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

sql-query-mcp

by andyWang1688
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

run_select

Run read-only SQL queries (SELECT or CTE) against a connected database with an optional row limit.

Instructions

Run 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": "run_select"
  }
}

Input Schema

NameRequiredDescriptionDefault
sqlYes
limitNo
connection_idYes

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.6/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 discloses the read-only nature, which is critical for safety, but lacks further behavioral traits such as timeouts, response structure, or rate limits. A more detailed description would be beneficial.

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?

The description is a single sentence of 7 words, extremely concise and front-loaded with the key purpose. However, it could be slightly more informative without sacrificing conciseness.

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?

Given no output schema, the description should explain what the tool returns (e.g., rows, columns, success indication). It also lacks information about error handling or prerequisites (e.g., connection must be live). This leaves the agent with incomplete context for using the tool reliably.

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%, meaning no parameter descriptions exist in the schema. The description adds no additional meaning beyond the parameter names (sql, limit, connection_id). It does not explain the purpose of limit, the format of sql, or how connection_id is used.

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 a read-only SELECT or CTE query. It specifies the verb 'run', the resource 'query', and the scope 'read-only', effectively distinguishing it from sibling tools like start_query (presumably for writes) and other non-query tools.

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 explicitly indicates the tool is 'read-only', which guides the agent to use it only for queries that do not modify data. It implies when not to use (for DML operations), but does not name alternatives like start_query for writes or explain_query for analysis.

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