Skip to main content
Glama

Keep first row per composite key

bpj_table_dedupe_by_key
Read-onlyIdempotent

Keep the first record for each composite key, preserving source order.

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>",
      "columns": "<columns>"
    },
    "name": "bpj_table_dedupe_by_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
columnsYes

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?

The annotations already establish that this is a safe, read-only, idempotent, non-destructive operation. The description adds useful behavioral detail—first-occurrence semantics and source-order preservation—but omits output shape and other duplicate-handling details.

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 one short, front-loaded sentence with no filler and a clear ordering guarantee. It is efficient, though extremely terse for a tool with undocumented required inputs.

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?

With two required string parameters, no output schema, and 0% schema description coverage, the definition leaves both input encoding and result format undocumented. For a data-transformation tool, that is a significant completeness gap.

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 must compensate for both required parameters. It only alludes to composite key fields and never explains that rows is a JSON record array or how columns encodes the key fields.

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 states a specific operation—keeping the first record per composite key—and a concrete ordering guarantee. It is clearly distinct from generic duplicate detection, though it does not name a sibling tool or explicit exclusion.

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?

It gives no when-to-use or when-not guidance. It also does not clarify that rows must be a JSON record array or how composite key columns are specified, leaving the agent to infer usage from the schema and title.

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.