Skip to main content
Glama

BRAINIAC CRM Data Intelligence

Detect duplicate contacts

crm-intelligence_duplicate-contact-detect

Find duplicate contacts with explainable rules and confidence levels. Different email addresses are not treated as the same person. Safe merge suggestions copy only empty fields and do not change a CRM. Price $0.05 USDC. POST /api/v1/crm-intelligence/duplicate-contact-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": "crm-intelligence_duplicate-contact-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
contactsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: it discloses the cost ($0.05 USDC), the payment failure mode (402, no execution), and that merge suggestions copy only empty fields and do not mutate the CRM. The main gap is that it says nothing about the response shape or how matches/confidence are returned.

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?

Sentences are short and front-loaded, with the purpose and the email-identity rule leading. The endpoint path and payment boilerplate are lower value but do earn their place for an agent that must handle 402s.

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?

No output schema and no annotations mean the description must be self-sufficient, and it covers cost, failure mode, and non-mutation well. However, for a tool with three alternate input modes and a nested file object, the total silence on input format leaves a significant hole an agent cannot resolve from structured fields alone.

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% and there are four parameters, three of which (csv, json, file with nested mediaType/fileBase64) are alternative input encodings whose mutual exclusivity is critical and completely undocumented. The description never mentions how contacts are supplied, so it fails to compensate for the coverage gap.

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 and resource ('Find duplicate contacts') plus the differentiating trait of explainable rules and confidence levels, which separates it from the sibling duplicate-company-detect by resource. It does not explicitly name any sibling, so the differentiation is implied by the resource rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage ('find duplicates', 'safe merge suggestions') and clarifies a key semantic boundary (different emails are not the same person), but it never states when to choose this over contact-normalize or duplicate-company-detect, nor what input shape to prefer. Guidance is implied rather than explicit.

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