ParseHub.dev (documents to records)

analyze_csv

Analyze a CSV file. operations is a JSON list of filter, sort, drop_columns, rename_columns, fill_na, drop_na, or group_by steps.

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": {
      "file_path": "<file_path>",
      "operations": "<operations>"
    },
    "name": "analyze_csv"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes
`operations`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 25, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are provided to supplement behavioral traits. The description focuses solely on defining input parameters, providing no context on performance, data handling limitations, or the structure of the eventual output.

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 tool is concisely described in two focused sentences. The description prioritizes the overall goal before detailing the complex structure of the required inputs.

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

Completeness4/5

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

Given the lack of output schema and 0% coverage, the description is reasonably complete by detailing the functional constraints of the `operations` parameter, which is the most complex input.

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

Parameters4/5

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

With 0% schema coverage, the description is highly valuable as it defines the expected content and functionality of the `operations` field by listing all possible steps (e.g., drop_columns, fill_na). Note: The description contradicts the schema, stating it is a 'JSON list' when the schema defines it as a 'string'.

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 clearly identifies the tool's core function: analyzing a CSV file. It distinguishes its action from general document or database extraction tools by focusing on data transformation steps rather than simple summarization.

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 specifies the nature of the `operations` parameter, listing acceptable actions (e.g., filter, sort, group_by). This implicitly guides the user toward using this tool when complex data manipulation is required.

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

All ParseHub.dev (documents to records) tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?