Skip to main content
Glama

BRAINIAC Data Quality Intelligence

Profile CSV columns

data-quality_csv-profile

Count present, missing, and distinct values for each column and report the minimum and maximum of the supplied values. Price $0.04 USDC. POST /api/v1/data-quality/csv-profile. 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-profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
recordsNo
keyColumnsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose genuinely useful non-obvious behavior: pricing ($0.04 USDC), the endpoint, and the 402 failure mode for unpaid calls. It does not state limits (row/column caps), what happens when neither csv nor file nor json nor records is supplied, or how keyColumns affects the distinct counts.

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?

Three short sentences, front-loaded with the capability before billing and transport details. Every sentence carries information; no filler or restatement of the tool name.

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?

A five-parameter tool with nested objects, mutually exclusive-looking input encodings, and no output schema receives only a one-line description of results and no input documentation. The billing/402 note is thorough, but the input contract an agent must satisfy to get a successful call is entirely absent.

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?

Schema description coverage is 0% across five parameters, including a nested file object with mediaType and fileBase64, and the description adds nothing. An agent cannot tell from either source whether to pass `csv`, `json`, `file`, or `records`, nor what `keyColumns` does (presumably grouping or distinct-key computation). 'the supplied values' is the only faint hint about input.

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: counts present, missing, and distinct values per column plus min/max of supplied values. An agent knows exactly what it gets back. It does not differentiate itself from siblings such as data-quality_csv-missing-value-audit or data-quality_csv-column-type-detect, which overlap conceptually with the missing-count and value-range output.

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 when-to-use guidance and no named alternatives, despite seven closely related csv-* siblings. The only conditional instruction is about payment ('Unpaid calls return 402 and do not run'), which is operational 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