Skip to main content
Glama

BRAINIAC Data Quality Intelligence

Propose CSV normalization

data-quality_csv-normalize

Propose trim, email lowercase, boolean tokens, and unambiguous thousands separators. Each change names its rule and keeps the original cell. Dates that are not already YYYY-MM-DD are not rewritten. Price $0.04 USDC. POST /api/v1/data-quality/csv-normalize. 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-normalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
recordsNo
keyColumnsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value: proposals are non-destructive (each change names its rule and preserves the original cell), dates outside YYYY-MM-DD are left alone, the call costs $0.04 USDC, and unpaid calls return 402 without running. However, it never says what the response contains (proposal list, counts, or acceptance mechanism), which is a meaningful gap for a tool with 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?

The transformation list is front-loaded and the payment/endpoint facts are packed into short sentences with little waste. Slightly terse to the point of omitting needed input guidance, but not padded.

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?

This is a nested-object, five-parameter, zero-annotation, no-output-schema tool, so the description needs to do heavy lifting on inputs and results. It covers pricing and the non-rewrite rule but leaves the parameter roles and the returned proposal shape entirely undocumented.

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 (csv, file, json, records, keyColumns), and the description adds no meaning to any of them. It implies cell-level work but never explains the input-mode choice between csv/file/json/records or what keyColumns is for, leaving an agent to reverse-engineer the 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?

The description names the specific transformations it proposes (trim, email lowercase, boolean tokens, thousands separators) on CSV cells, so the verb 'propose' plus the concrete rule list makes the operation identifiable. It doesn't explicitly contrast itself with the sibling audit/detect tools, but the proposal framing is distinct enough that an agent can differentiate.

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 statement of when to use this versus the sibling detect/audit/profile tools, nor any prerequisite such as profiling first. Usage is only inferable from the operation list itself, and no exclusions or alternatives are offered.

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