Skip to main content
Glama
Sign In
EspoCRM Assistant

EspoCRM Assistant

by The-Keep-Studios
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

crm_duplicate_candidates

Identify duplicate records by scanning specified fields to find matching candidates in your CRM data.

Instructions

Find possible duplicates from identifying fields.

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": {
      "fields": "<fields>"
    },
    "name": "crm_duplicate_candidates"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior1/5

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

No annotations are provided, so the description carries full burden. It states 'Find possible duplicates' but does not disclose any behavioral traits such as whether results are returned, if it is read-only, or what happens with the fields parameter. The description is insufficient for an agent to understand side effects or constraints.

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

Conciseness2/5

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

The description is very short, but it is under-specified rather than concise. A single sentence that lacks necessary details does not earn high marks for conciseness.

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

Completeness1/5

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

Given a complex object parameter, no output schema, and no annotations, the description is severely inadequate. It does not explain the return format, how the fields object affects results, or any constraints, leaving the agent with insufficient context to use the tool correctly.

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

Parameters1/5

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

The schema coverage is 0%, and the description only mentions 'identifying fields' without explaining the structure or expected keys/values of the 'fields' parameter. The agent cannot infer how to populate the object parameter correctly.

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 clearly states the tool finds possible duplicates using identifying fields, with a specific verb and resource. It implicitly contrasts with sibling tools like crm_get (single record) and crm_search (general search), but does not explicitly differentiate.

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?

No guidance is provided on when to use this tool versus alternatives like crm_search or crm_get. The description lacks context about prerequisites, typical use cases, or when not to use it.

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