Skip to main content
Glama

BRAINIAC Data Quality Intelligence

Detect CSV column types

data-quality_csv-column-type-detect

List the observed types in each column. A value that differs from the most common type is referenced by row and column and is not changed. A tie is not blamed on a row. Price $0.04 USDC. POST /api/v1/data-quality/csv-column-type-detect. Unpaid calls return 402 and do not run.

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": "data-quality_csv-column-type-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
recordsNo
keyColumnsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations, the description still discloses meaningful behavior: results are descriptive only ('is not changed'), tie handling is defined, cost is $0.04 USDC, and unpaid calls 402 without running. However it omits permission/rate context and says nothing about the shape of the response or how ties and mismatches are structured beyond 'referenced by row and column'.

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?

Sentences are short and front-loaded with the core behavior, but the phrasing is terse to the point of ambiguity ('A tie is not blamed on a row') and the endpoint/payment lines sit awkwardly after the semantic content. Little waste, but the ordering buries the cost and 402 caveats mid-paragraph.

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 tool with no output schema and no annotations, the description does convey what is produced conceptually (per-column observed types, out-of-type values flagged by row/column without mutation) plus cost and failure behavior. It is still incomplete on input selection among four alternative payload parameters and on the exact return structure.

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

Parameters1/5

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

Five parameters including a nested file object, with 0% schema description coverage, and the description says nothing about any of them. It never explains whether csv, json, records, or file are alternatives, nor what keyColumns does (e.g., whether it affects tie-breaking or type constancy checks), so an agent must guess which input to supply.

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?

States a specific verb and resource: 'List the observed types in each column', which tells an agent this is a type-inference/reporting operation rather than normalization or schema detection. It does not explicitly contrast itself with siblings such as csv-schema-detect or csv-normalize, but the purpose is unambiguous.

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 guidance, no prerequisites, and no mention of when this differs from sibling audit tools like schema-detect or missing-value-audit. The only conditional present is the payment gate (unpaid calls return 402), which is invocation mechanics rather than usage guidance.

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