Export database query results as CSV or JSON for portable data transfer and analysis.
Export query results as CSV or JSON format. Useful for getting data out of the database in a portable format.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max rows (default: 100, max: 1000) | |
| query | Yes | SQL query or MongoDB JSON query | |
| format | No | Output format (default: csv) | |
| connection | No | Connection alias (default: 'default') |
Changes observed during successful MCP inspections.
v1.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the full behavioral burden. It discloses format options and portability but omits critical traits: whether export writes files server-side or returns content, read-only vs mutation, permission requirements, row-limit behavior, and error handling.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences, front-loaded with the action and formats. The second sentence is slightly padding but not harmful, so the definition remains appropriately concise.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a four-parameter tool with no output schema and no annotations, the description leaves too much unspecified. An agent cannot tell whether export_data returns inline data, a file path, or writes to disk, nor how it relates to run_query.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all four parameters are documented in the schema. The description only echoes the CSV/JSON format enum and adds no syntax, default, connection-alias, or limit detail beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (export) and resource (query results) plus supported formats (CSV/JSON). It does not differentiate from sibling run_query, which also executes queries, but the export framing is clear enough to identify the tool's core action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit when-to-use, prerequisites, or alternatives are provided. The second sentence is generic and does not tell an agent when to choose export_data over run_query or search_data.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.