csv-mcp

by meysam-kazemi

Overview Schema Source Related Servers Discussions Admin

Python

Local

create_csv

Create CSV or TSV files with configurable options and spreadsheet formula-injection protection.

Instructions

Create a CSV/TSV file with atomic output and formula-injection handling.

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": {
      "output_file": "<output_file>",
      "columns": "<columns>"
    },
    "name": "create_csv"
  }
}

Input Schema

Name	Required	Default
`rows`	No
`columns`	Yes
`options`	No
`overwrite`	No
`output_file`	Yes
`column_types`	No
`spreadsheet_formula_policy`	No	escape

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 29, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Without annotations, the description adds value by noting atomic output and formula-injection handling, but omits other behaviors like overwrite policy (which is in the schema). Could be more explicit.

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?

Single sentence, no wasted words. However, it could benefit from brevity with more structure (e.g., bullet points for features).

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 7 parameters and 13 siblings, the description is too sparse. It doesn't explain 'atomic output' or how formula injection is handled, missing critical context.

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?

Description does not explain any parameters; schema coverage is 0%. The mention of formula-injection handling vaguely relates to the spreadsheet_formula_policy parameter, but no specifics.

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 states the tool creates a CSV/TSV file and mentions two key features (atomic output and formula-injection handling). It distinguishes from sibling tools like read_csv or query_csv, though the name only mentions CSV.

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?

No guidance on when to use this tool versus alternatives like append_rows or validate_csv. Lacks context for when creation is preferred over other operations.

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

Deploy Server