Skip to main content
Glama

CSV Profiler

profiler_csv

Détecte les types, cellules vides et ruptures de format dans un échantillon CSV avec en-tête.

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": {
      "csv": "<csv>",
      "separateur": "<separateur>"
    },
    "name": "profiler_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYes
separateurYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 behavioral burden and mostly does not. 'Détecte' implies a read-only analysis rather than a mutation, but the description says nothing about what a format break is reported as, whether the whole input is scanned, or what the caller receives back.

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?

A single front-loaded sentence with no filler; every word (including 'échantillon' and 'avec en-tête') carries information. It is admittedly terse given how little else is documented, but nothing is wasted.

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?

No output schema, no annotations, and 0% parameter coverage leave the description as the only source of information, and it does not explain the result shape or the delimiter's role. For a diagnostic tool whose value depends on how findings are reported, this leaves the caller guessing.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate, and it partially does: 'échantillon ... avec en-tête' adds a real constraint not encoded in the schema (a header row is expected). However, the 'separateur' parameter is never mentioned and the description does not relate the delimiter choice to format-break detection.

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 action ('Détecte') and three concrete findings (types, empty cells, format breaks) scoped to a CSV sample, so an agent knows exactly what analysis it performs. There are no sibling tools to differentiate from, which is the only reason it falls short of a 5.

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 call this versus doing something else, no prerequisites, and no exclusions. The phrase 'échantillon CSV avec en-tête' implies the input must include a header row, but the caller is left to infer that constraint and any limits on sample size.

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