Skip to main content
Glama

Profile CSV column quality

bpj_profile_csv
Read-onlyIdempotent

Count blanks, populated cells, distinct values and repeats per CSV column.

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>"
    },
    "name": "bpj_profile_csv"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds that the analysis is per-column and lists the four statistics computed, which is genuine context beyond the annotations. It stops short of saying whether the header row is excluded, how missing columns are handled, or how the results are returned.

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, and the metrics are enumerated in a scannable order. It is slightly cryptic in places — 'repeats' and 'populated cells' could be defined more precisely — but nothing is wasted.

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

Completeness3/5

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

For a one-parameter, read-only tool this is close to adequate, but with no output schema the description should say what the tool returns (presumably per-column counts, in what shape). The input contract — full CSV text including a header row, 12000-character cap — is also never spelled out.

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?

One parameter with 0% schema description coverage; the only hints are the schema title 'CSV with headers' and a maxLength of 12000. The description's phrase 'per CSV column' indirectly confirms that the first row supplies headers and that the input is a single raw CSV string, but it neither states the format requirement explicitly nor mentions the size limit.

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 a specific verb (Count) and resource scope (per CSV column) and enumerates the computed metrics: blanks, populated cells, distinct values, repeats. An agent can tell this is a column-profiling tool. It does not, however, discriminate against near neighbors such as bpj_profile_json_records or bpj_pivot_csv_counts.

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 when-to-use or when-not-to-use guidance and no named alternative. The agent must infer from the metrics that this is for data-quality inspection of a CSV rather than conversion (bpj_csv_to_json) or aggregation (bpj_pivot_csv_counts).

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.