DataSearcher MCP

by MarkIvor

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

export_data

Export data from a database table or custom SQL query into a CSV file for offline analysis or sharing.

Instructions

Экспорт данных в CSV-файл.

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": {
      "table_name": "<table_name>"
    },
    "name": "export_data"
  }
}

Input Schema

Name	Required	Description	Default
`sql`	No
`columns`	No
`filename`	No
`table_name`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 1, 2026

TDQS

C2.4/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only says 'export data to CSV'. It does not reveal side effects, file handling, whether existing files are overwritten, permissions needed, or what the operation returns.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short and front-loaded, but it is under-specified rather than appropriately concise. A single phrase with no parameter or usage context does not earn its place as a complete tool definition.

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?

For a tool with four parameters, no annotations, and a generic purpose, the description is far from complete. Although an output schema exists and may describe return values, the description still omits essential detail about how to use the parameters and when this tool is appropriate.

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 description does not explain any of the four parameters: table_name, sql, columns, or filename. The agent is left without guidance on what data gets exported, how filtering works, or how the output file name is determined.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete action, 'export', and a concrete target format, 'CSV file', which makes the tool's core purpose understandable. It implicitly differentiates from the sibling export_xlsx by format, though it does not clarify what data is exported or how it is selected.

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

Usage Guidelines2/5

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

There is no guidance about when to use this tool rather than alternatives such as export_xlsx, nor any explanation of prerequisites or typical contexts. The intended use must be inferred entirely from the tool name and format mention.

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