Skip to main content
Glama

BRAINIAC Data Quality Intelligence

Report CSV quality

data-quality_csv-report

Combine the schema, profile, missing cells, duplicate groups, possible outliers, and proposed normalization for one supplied table. No record is removed and no outlier is confirmed. Price $0.12 USDC. POST /api/v1/data-quality/csv-report. 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-report"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
recordsNo
keyColumnsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a lot: it discloses non-destructive semantics ("no record is removed and no outlier is confirmed"), the price ($0.12 USDC), the HTTP endpoint, and the payment-gating behavior (402 on unpaid, no execution). Remaining gaps are which of the several input forms to supply and what the response envelope looks like.

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?

Four short sentences, front-loaded with the tool's function before operational details. The price and endpoint lines earn their place given payment gating, though the endpoint path is the least informative for tool selection.

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?

Without annotations or an output schema, the description compensates well on output contents and destruction/payment semantics, but a 5-parameter tool with 0% schema coverage and no required fields needs to clarify which input form is expected and the role of `keyColumns`. Those omissions leave an agent guessing at invocation.

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 5 parameters including a nested `file` object, and the description only gestures at "one supplied table" without explaining when to use `csv` vs `json` vs `file` vs `records`, or what `keyColumns` does for duplicate grouping. It adds almost no meaning beyond the bare schema.

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 ("combine") and enumerates exactly what is produced: schema, profile, missing cells, duplicate groups, possible outliers, proposed normalization. This implicitly distinguishes it from the single-purpose siblings (profile, duplicate-row-detect, outlier-detect, etc.) as the one-shot aggregate, though it never names them explicitly.

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?

"for one supplied table" establishes scope and the aggregation framing implies the when-to-use against the individual sibling analyses, but this must be inferred. There is no explicit statement such as "use this instead of calling the individual analysis tools" and no when-not 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