Skip to main content
Glama

Duplicate key occurrences

bpj_dq_duplicate_key
Read-onlyIdempotent

Return repeated key values with all associated row numbers.

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>",
      "column": "<column>"
    },
    "name": "bpj_dq_duplicate_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a modest amount by indicating that the output pairs each repeated value with every row number where it occurs, which is real return-shape information since there is no output schema. It says nothing about ordering, limits, or how the input rows are parsed.

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?

A single short sentence, front-loaded with the verb and result, with no wasted words. Its brevity edges into under-specification rather than padding, which is the better failure mode.

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?

Two required parameters are entirely undocumented by the schema and unexplained by the description, and no output schema exists to clarify the return shape. For a tool whose input format (a JSON string array) is non-obvious, the description leaves an agent with real invocation risk.

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%, so the description carries the full burden for two required parameters, and it does not meet it. 'Key values' loosely gestures at the 'column' parameter, but nothing explains that 'rows' must be a JSON-encoded record array (max 12000 chars) or what column syntax is accepted.

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 specific verb ('Return') and a specific resource ('repeated key values with all associated row numbers'), so an agent understands this is a duplicate-value detection tool. It does not, however, distinguish itself from the sibling 'bpj_dq_duplicate_rows', which sounds like it targets the same problem from a different angle.

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 when-to-use guidance, no prerequisites, and no mention of the near-identical sibling 'bpj_dq_duplicate_rows'. The agent must guess which duplicate-checking tool applies to a given task.

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.