Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getPersonByEmail

Read-onlyIdempotent

Look up a contact by email in Follow Up Boss CRM and return the matching person or ambiguity candidates for disambiguation.

Instructions

Look up one person by email. Returns the contact, or an ambiguity result with candidate IDs. Use this to find a contact; use listPeople for other filters.

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": {
      "email": "<email>"
    },
    "name": "getPersonByEmail"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailYesEmail address to look up.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.0
    • changedInput schema / properties / email / description
      Previous value: -"Email address to look up"New value: +"Email address to look up."
  2. First observedv1.1.1

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: a lookup can yield an ambiguity result with candidate IDs rather than a single contact. It says nothing about what to do with those candidates or whether such a lookup could create anything (it cannot), but that is largely implied by the annotations.

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?

Three short sentences, no filler: purpose, return behavior, and alternative are each stated once and front-loaded. Nothing repeats the name or title, and nothing could be cut without losing information.

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 tool without an output schema, the description covers purpose, the non-obvious ambiguity return, and the sibling boundary. The one gap is that it does not say how to resolve an ambiguity result (e.g., by ID), leaving the follow-up step implicit.

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 there is a single required parameter already documented as "Email address to look up." The description adds no format, normalization, or case-sensitivity detail beyond that, so the schema carries the full load and the baseline 3 applies.

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 ("Look up one person by email") with the key constraint baked in: exactly one person, keyed by email. It names the sibling listPeople and the condition under which that sibling applies, so an agent can distinguish the two 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 Guidelines4/5

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

Explicitly routes to listPeople for other filters, which is the main alternative an agent would weigh. It does not mention getPerson (the by-ID sibling) or what to do when the ambiguity result is returned, so the guidance is clear but not fully exhaustive.

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