Skip to main content
Glama

BRAINIAC Data Quality Intelligence

Detect duplicate CSV rows

data-quality_csv-duplicate-row-detect

Group records that match after trimming each compared cell. When key columns are supplied, only those columns are compared. No record is removed. Price $0.05 USDC. POST /api/v1/data-quality/csv-duplicate-row-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-duplicate-row-detect"
  }
}

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 usefully discloses non-destructive behavior ('No record is removed'), pricing, and unpaid-call behavior (402, no execution). However, it does not explain return format, authentication, rate limits, or how the input modes behave, leaving important behavioral gaps for a tool with no annotation coverage.

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 description is short, front-loaded with core matching behavior, and avoids unnecessary elaboration. Operational details such as price, endpoint, and unpaid-call handling are relevant, though they occupy space that could have documented input modes.

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 relatively complex tool with five undocumented input parameters, nested file input, no annotations, and no output schema. The description covers matching semantics, non-destruction, and payment handling, but omits how the alternate inputs work and what the tool returns, which is insufficient for reliable 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 five parameters, and the description only explains keyColumns. It adds no meaning for csv, file, json, or records, including how those alternate input sources should be selected or formatted.

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 first sentence states specific matching behavior: records are grouped after trimming compared cells. The keyColumns condition further clarifies duplicate detection, though the description never explicitly says 'duplicate rows' or distinguishes itself from sibling detection/audit tools without relying on the title.

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 explicit when-to-use or when-not-to-use guidance, and no alternative sibling is named. The keyColumns sentence describes a parameter condition rather than directing the agent to this tool over related CSV quality tools.

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