Skip to main content
Glama

BRAINIAC CRM Data Intelligence

Detect duplicate companies

crm-intelligence_duplicate-company-detect

Find duplicate companies by a normalized domain or company-name key, and flag fuzzy name matches with a confidence level. Different domains are not merged. Suggestions do not change a CRM. Price $0.05 USDC. POST /api/v1/crm-intelligence/duplicate-company-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-company-detect"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
fileNo
jsonNo
companiesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does so well: it declares the operation is non-mutating, states the dedupe rule (different domains are not merged), notes fuzzy matches carry a confidence level, and discloses pricing plus that unpaid calls return 402 and do not execute. What it omits is the shape of the response and any limits on input volume, so it falls short of full behavioral coverage.

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?

Front-loaded with the matching behavior and non-merge rule, then operational facts. Every sentence carries information, though the raw POST path is somewhat redundant with the tool identity and pushes the operational constraints toward the end.

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?

The tool has nested input objects, zero schema descriptions, and no output schema, so the description should do more work. It partially compensates by explaining match keys and that fuzzy results carry a confidence level, but it never explains what the suggestion set looks like or how to select among the four input formats, leaving meaningful gaps for a moderately complex tool.

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% across four top-level parameters, including a nested company object with ten undocumented fields, so the description must compensate. It only clarifies the matching keys (domain, name) and says nothing about the four mutually exclusive input channels (csv, json, file, companies) or which to choose, which is the single highest-risk ambiguity for this tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Find duplicate companies") plus the matching keys used (normalized domain or company-name key) and the fuzzy-match/confidence behavior. The resource is explicit enough to separate it from the sibling duplicate-contact-detect without opening either schema.

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 matching rules imply usage ("Different domains are not merged" tells the agent which cases will not appear as duplicates), and "Suggestions do not change a CRM" signals a read-only pass. However, there is no explicit when-to-use, when-not-to-use, or routing to alternatives such as company-normalize or duplicate-contact-detect, leaving the agent to infer the workflow position.

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