sql-query-mcp

export_query_file

Export read-only SQL query results to CSV or XLSX files on your local machine.

Instructions

Export a read-only query result to a local CSV or XLSX file.

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>",
      "output_path": "<output_path>"
    },
    "name": "export_query_file"
  }
}

Input Schema

Name	Required	Default
`sql`	Yes
`limit`	No
`format`	No	csv
`file_name`	No
`overwrite`	No
`export_all`	No
`output_path`	Yes
`connection_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.4.0May 23, 2026

TDQS

B3/5.0

Behavior2/5

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

With no annotations, the description carries full burden. It only notes read-only, but fails to disclose side effects, file location, or behavior of parameters like overwrite and export_all. Important behaviors are omitted.

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 concise sentence that front-loads the core action. It is appropriately sized but could include more detail without becoming verbose.

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 8 parameters, no output schema, and no annotations, the description is inadequate. It does not cover required parameters, output format details, or behavior nuances, leaving significant gaps.

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%, so description must explain parameters. It only mentions CSV and XLSX (format), but ignores all other 7 parameters including required ones like SQL and connection_id. No additional meaning is provided.

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 exports a read-only query result to CSV or XLSX files. It uses a specific verb-resource pair and distinguishes from siblings like run_select and import_table_file.

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 it's for read-only operations but does not explicitly state when to use this tool over alternatives or when not to use it. No alternatives are mentioned.

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

Deploy Server