Skip to main content
Glama

CSV column profile: type, distinct, missing, min and max per column

submit_csv_column_profile
Idempotent

Profile every column of a CSV: inferred type (number, integer, date, email or text), non-empty and missing counts, distinct values, and min/max for numeric columns. Choose this for a per-column picture of a CSV: inferred type, non-empty and missing counts, distinct values, and min/max for numeric columns. Do not choose this when you want the file diagnosed for import errors (use csv-preflight) or a completeness report (use csv-missing-value-report). Example requests: Profile the columns of this CSV before I load it. | Profile which CSV column is numeric and what is its range? | How many distinct values are in each CSV column? Profile this file.

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": {
      "inputs": "<inputs>",
      "authorized_by": "<authorized_by>"
    },
    "name": "submit_csv_column_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsYes
quote_idNoThe quote_id returned by POST /v1/jobs. Required to authorize a priced capability; the service rejects a priced job that does not name the quote it issued.
authorized_byYesIdentifier of the human or agent authorizing this job.
accepted_priceNoThe amount accepted, exactly as quoted (for example "5.00" or 5). Checked against the stored quote, so a price that moved between quote and authorize is refused rather than silently absorbed. Optional, but sent to make the acceptance explicit.

Output Schema

NameRequiredDescriptionDefault
quoteNo
stateYes
job_idYes
artifactsNo
access_tokenNoPer-job credential. Present it as the X-Job-Token header to read the job or list it. Keep it; it is the only credential for this job.
verificationNoIndependent verification. verification.ok = false means the job failed, not a partial success.
capability_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is carried by structured data. The description adds nothing behavioral beyond that: it does not mention that this is a priced capability requiring a quote and an authorizing principal, nor the 1 MB input ceiling. It does not contradict the annotations, but the pricing/authorization workflow is a notable undisclosed trait.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The output-field list is repeated almost verbatim in the first and second sentences ('inferred type, non-empty and missing counts, distinct values, and min/max for numeric columns' twice), which is pure waste. The example block is useful but has a stray trailing fragment ('Profile this file.') appended after the third example, making the ending feel tacked on rather than front-loaded.

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

Completeness4/5

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

For a tool with four parameters, a nested input object and an output schema, the description is complete on what is measured and which sibling to prefer; return shape need not be explained because an output schema exists. The gaps (price/quote workflow, size limit) are recoverable from the schema descriptions, so nothing blocks correct invocation.

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?

The description says nothing about any of the four parameters; all meaning comes from the schema, which at 75% coverage documents content, quote_id and authorized_by in useful detail. Baseline 3 is appropriate here, but the description could have flagged that content is the raw CSV text and that quote_id is mandatory for a priced job.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a concrete verb and resource ('Profile every column of a CSV') and enumerates the exact outputs: inferred type with a type vocabulary (number, integer, date, email, text), non-empty and missing counts, distinct values, and min/max for numeric columns. It also names the sibling tools it is not (csv-preflight, csv-missing-value-report), so an agent can distinguish it without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit selection guidance is present in both directions: 'Choose this for a per-column picture' and 'Do not choose this when you want the file diagnosed for import errors (use csv-preflight) or a completeness report (use csv-missing-value-report)'. Example requests further anchor the intended calls.

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