Skip to main content
Glama

BRAINIAC Data Quality Intelligence

Audit missing CSV values

data-quality_csv-missing-value-audit

Find empty or whitespace-only cells and give each one a row and column reference. The row stays in the table. Price $0.03 USDC. POST /api/v1/data-quality/csv-missing-value-audit. 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-missing-value-audit"
  }
}

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?

With no annotations supplied, the description carries the full burden and does disclose some real behavior: the audit is non-mutating, it costs $0.03 USDC, it is a POST to a specific endpoint, and unpaid calls return 402 without executing. Those are useful operational facts. It says nothing about output shape, size limits, or how the five input modes interact, which matters for a tool with a 12MB file field and a 5000-record array.

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?

Sentences are short and the purpose is front-loaded, followed by the behavioral constraint and then commercial/transport facts. The endpoint string is arguably redundant for an MCP caller, but nothing is padded or buried. Four of five sentences carry actionable information.

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 tool with five undocumented parameters, a nested object, a boolean alternative input modes, no annotations, and no output schema, the description is thin. It never explains how the row/column references are returned or how to pick among the four data inputs, which is exactly what an agent needs before calling.

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 (mediaType/fileBase64/filename), and the description adds no parameter meaning at all. It never explains whether csv, file, json, and records are mutually exclusive alternatives or which keyColumns does. An agent must guess the input mode from the JSON schema alone.

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 gives a concrete verb and object: find empty or whitespace-only cells and return a row/column reference for each. That is far more specific than the title alone and an agent can tell it is a detection audit rather than a cleanup pass, reinforced by 'The row stays in the table.' It stops short of explicitly contrasting itself with siblings like csv-profile or csv-normalize.

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 choose this over csv-profile, csv-schema-detect, or csv-normalize. The only hint is the implied non-destructive framing ('The row stays in the table'), which tells an agent the data is not modified but not when this tool is the right pick. No prerequisites, no exclusions.

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