Skip to main content
Glama

Exact duplicate row locations

bpj_dq_duplicate_rows
Read-onlyIdempotent

Match complete records by column and point repeated rows to their first occurrence, distinguishing missing from null.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rows": "<rows>"
    },
    "name": "bpj_dq_duplicate_rows"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description usefully adds that output is locations anchored to the first occurrence and that missing cells are treated distinctly from nulls — a real semantic detail not derivable from annotations.

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?

One tight sentence with the core behavior front-loaded and no filler. The phrase 'by column' is slightly ambiguous but does not waste space.

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?

For a read-only, single-parameter analysis tool with rich annotations and no output schema, the description covers the conceptual behavior and hints at return values. It falls short on input format, which is the main practical unknown an agent faces when constructing the 'rows' payload.

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% for the single required 'rows' parameter, so the description must carry this burden. 'Match complete records by column' hints that input is record-oriented, but it never states that the parameter is a JSON record array, its size limit, or the expected shape of each record.

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 a specific operation on a specific resource: matching complete records and pointing repeated rows to their first occurrence. 'Complete records' implicitly contrasts with key-based duplication (bpj_dq_duplicate_key), but that sibling is never named, so differentiation is left to inference.

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, when-not-to-use, or alternative pointer. An agent must infer that this is the tool for whole-row duplicates rather than key or sparse-row checks; nothing in the text routes it between bpj_dq_duplicate_rows, bpj_dq_duplicate_key, and bpj_dq_sparse_rows.

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.