Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

checkDuplicate

Read-onlyIdempotent

Check whether a contact already exists in Follow Up Boss by email or phone before creating a new record, helping prevent duplicate person entries in the CRM.

Instructions

Check if a person already exists by email or phone

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": "checkDuplicate"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoEmail to check
phoneNoPhone to check

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds no behavior beyond that: it does not say what a match looks like, how partial or multiple matches are handled, or whether the check is exact-match only.

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 front-loaded sentence with no filler or redundancy. It is efficient, though the terseness leaves the definition under-specified in ways other dimensions penalize.

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

Completeness2/5

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

There is no output schema, so the description should explain the return value, but it never says whether the result is a boolean, a person record, or a match list. For a lookup tool whose entire value is the shape of its answer, this is a significant omission.

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 coverage is 100%, so both parameters are already documented, and the description only echoes them with 'by email or phone'. The 'or' hints that either identifier is acceptable, but it never clarifies whether both may be sent together or how conflicting results are resolved, so the added meaning is marginal.

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: check whether a person already exists, keyed on email or phone. That is clear enough to act on, but it never distinguishes this from sibling lookups such as getPersonByEmail or listPeople, which overlap in intent.

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 explicit when-to-use guidance: nothing says this is a pre-creation dedupe check, nothing says whether email, phone, or both should be supplied, and no alternative (getPersonByEmail, listPeople, searchPeopleByTag) is named. The agent must infer the workflow context entirely.

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