Skip to main content
Glama
Sign In
csv-mcp

csv-mcp

by meysam-kazemi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

preview_csv

Preview a limited number of rows and specific columns from any CSV file, with adjustable parsing settings.

Instructions

Read a bounded page and optional subset of columns.

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": {
      "path": "<path>"
    },
    "name": "preview_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
limitNo
offsetNo
columnsNo
optionsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations provided, so the description carries full burden. It implies a read operation but does not explicitly state read-only behavior, side effects, or permissions. The phrase 'bounded page' hints at limited data retrieval but lacks specificity.

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?

Extremely concise single sentence that front-loads the core action. Every word is purposeful with no redundancy.

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 the complexity (5 parameters, nested options object, no annotations or schema descriptions), the description is too brief. It lacks context on how to use options, what the output contains, and when to choose this tool over others. The output schema exists but is unmentioned.

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?

Schema coverage is 0% with no parameter descriptions. The description only vaguely references 'bounded page' and 'optional columns', which map to limit/offset and columns. It does not explain the complex options object or parameter usage details.

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 states the verb 'read' and resource 'bounded page and optional subset of columns', which indicates previewing a limited portion of a CSV. However, it does not explicitly distinguish from sibling tools like read_csv or inspect_csv, which may have similar purposes.

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. It does not mention scenarios where a full read or query might be more appropriate, nor does it provide any exclusions or prerequisites.

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

Deploy Server

Other Tools