Skip to main content
Glama

BRAINIAC Data Quality Intelligence

Detect a CSV schema

data-quality_csv-schema-detect

Infer a column type from the supplied CSV or JSON values. A column with more than one non-numeric type stays mixed. No value is rewritten. Price $0.03 USDC. POST /api/v1/data-quality/csv-schema-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-schema-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
recordsNo
keyColumnsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations at all, the description does useful work: it declares the multi-type-to-mixed rule, states 'No value is rewritten' (implying a pure read), gives the price, and warns that unpaid calls return 402 and do not run. It still says nothing about what is returned, error behavior, or size limits, which matters given there is no output schema.

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?

Short, front-loaded sentences with the behavioral rule stated early; little waste. The endpoint path 'POST /api/v1/data-quality/csv-schema-detect' adds little for an agent and could be dropped.

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?

For a five-parameter tool with a nested file object, no annotations, and no output schema, the description leaves the return shape, input-mode selection, and keyColumns semantics undocumented. An agent could invoke it but cannot predict the result or choose inputs confidently.

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 five parameters, including a nested file object and a keyColumns array that are entirely undefined. The description only echoes 'CSV or JSON values' and never mentions file, records, or keyColumns, so it fails to compensate for the coverage gap.

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 verb+resource is concrete: infer a column type from supplied CSV or JSON values, with a stated mixed-type rule. However, the description frames it as per-column type inference while the name/title say 'CSV schema', and a sibling is literally 'csv-column-type-detect', so an agent may not immediately tell which one to pick.

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

Usage Guidelines3/5

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

It implies the input context ('supplied CSV or JSON values') but never says when to choose this over the sibling column-type-detect tool, nor which of csv/file/json/records to supply. Usage is inferable rather than stated.

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