Skip to main content
Glama

Cross-Channel Lead Deduplication

bpj_cross_channel_lead_deduplication
Read-onlyIdempotent

Reconcile unique online and event lead counts using the known overlap to quantify their exclusive and total reach.

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": {
      "online": "<online>",
      "events": "<events>",
      "overlap": "<overlap>"
    },
    "name": "bpj_cross_channel_lead_deduplication"
  }
}

Input Schema

NameRequiredDescriptionDefault
eventsYes
onlineYes
overlapYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/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 safety is covered. The description adds that this is a reconciliation using a 'known overlap', but omits what happens with inconsistent inputs and does not describe the returned values despite there being no output schema.

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 well-formed sentence that front-loads the action and the inputs, followed by the goal. No filler, though it is terse enough to leave the output shape ambiguous.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-integer, read-only computation the description covers the essential mechanics, and annotations cover the safety profile. The remaining gap is that it never says what the computation returns or how it behaves when overlap exceeds a channel count.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but each of the three integer parameters carries a self-explanatory title ('Unique online leads', 'Unique event leads', 'Leads present in both channels'). The description only reinforces that overlap is 'known' and used for reconciliation; it does not clarify units, bounds relationships, or error conditions beyond what titles imply.

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 verb ('Reconcile') and a specific resource ('unique online and event lead counts'), and states the output concept ('exclusive and total reach'). It is clearly distinguishable from the unrelated sibling names, though it gives no explicit sibling differentiation.

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 guidance on when to use this versus other counting or channel-mix tools, and no stated preconditions (e.g., that overlap should not exceed either channel count). The agent must infer applicability purely from the description.

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.