Skip to main content
Glama

data-api-code

csv_profile_and_query

Parse RFC-4180 CSV data and compute per-column types, null rates, distinct cardinalities, and numeric min/max/avg statistics.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "csv_profile_and_query"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo
delimiterNo,

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It usefully discloses what the output contains (per-column statistics), but says nothing about input precedence between text and filePath, error behavior on malformed CSV, size limits, or whether the call has side effects. For a tool with zero annotation coverage that is a notable gap.

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?

One sentence, front-loaded with the action and followed by the concrete outputs. Nothing is padded or redundant, and the enumerated statistics are the highest-value information available.

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?

With no annotations, no output schema, and 0% schema description coverage, the description should resolve the input-source ambiguity and any failure modes. It covers the compute side well but leaves an agent unable to determine how to supply input or what happens when a path is invalid.

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 description coverage is 0% across three parameters and none are required, yet the description never explains the text-versus-filePath choice, whether both may be supplied, which wins, or what delimiter does. It only implicitly gestures at CSV text via 'RFC-4180 CSV data', leaving the most consequential ambiguity unresolved.

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 specific verb (parse) and resource (RFC-4180 CSV data) and enumerates exactly what is computed: column types, null rates, distinct cardinalities, and numeric min/max/avg. That is far more informative than a restated name, though it never contrasts itself with a sibling such as json_to_csv_convert, which performs the opposite conversion.

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 statement of when to reach for this tool versus an alternative, and no mention of prerequisites or typical scenarios (e.g. profiling a file before loading it). The agent must infer the use case entirely from the purpose sentence.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources