Skip to main content
Glama
Sign In
Demo CRM MCP Server

Demo CRM MCP Server

by hayathi06
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_duplicates

Read-only

Checks an existing lead against every other lead and explains likely duplicates, so you can spot and resolve duplicate CRM records.

Instructions

Check an existing lead against every other lead and explain any likely duplicates.

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": {
      "lead_id": "<lead_id>"
    },
    "name": "find_duplicates"
  }
}

Input Schema

NameRequiredDescriptionDefault
lead_idYesThe lead's numeric id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds meaningful context beyond that: the scan is against 'every other lead' (full-corpus scope, implying cost) and the return is an explanation of likely duplicates rather than a bare list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence that front-loads the core action and stays free of filler. Nothing redundant or padded.

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 one-parameter read-only tool with annotations covering safety and closed-world scope, the description conveys scope (all other leads) and the nature of the output (explanations). No output schema exists, but the description adequately characterizes the response shape; only detailed return structure is left unspecified.

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 100% and the single lead_id parameter is documented as 'The lead's numeric id'. The description adds no format, range, or behavioral detail beyond the schema, so the baseline of 3 applies.

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?

States a specific verb (check) and resource (an existing lead vs every other lead) with the outcome being duplicate detection plus explanation. No sibling (get_lead, search_leads, pipeline_summary, etc.) performs duplicate detection, so the purpose is unambiguous even without an explicit sibling callout.

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?

Usage is implied by the description — call it to check one lead for duplicates — and the phrase 'existing lead' hints that the lead must already exist. However there is no explicit when-to-use, when-not-to-use, or alternative named, so guidance stays at the implied level.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools