Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getPerson

Read-onlyIdempotent

Retrieve a Follow Up Boss CRM person by ID and optionally include all fields or all custom fields to view complete profile data.

Instructions

Get one person by ID. Pass fields=allFields or allCustom to include custom 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": {
      "id": "<id>"
    },
    "name": "getPerson"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPerson ID.
fieldsNoComma-separated fields; allFields = everything, allCustom = all custom fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv2.0.0
    • changedInput schema / properties / fields / description
      Previous value: -"Comma-separated list of fields to return. Include custom field names (e.g. customClosingDate) to guarantee custom fields appear in the response"New value: +"Comma-separated fields; allFields = everything, allCustom = all custom fields."
    • changedInput schema / properties / id / description
      Previous value: -"Person ID"New value: +"Person ID."
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
  2. Changed1 schema field changedv1.5.1
    • changedInput schema / properties / fields / description
      Previous value: -"Comma-separated list of fields to return"New value: +"Comma-separated list of fields to return. Include custom field names (e.g. customClosingDate) to guarantee custom fields appear in the response"
  3. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this read-only, idempotent, non-destructive, and closed-world, so the safety profile is fully covered elsewhere. The one piece of added behavior is that custom fields are excluded unless fields=allFields or allCustom is passed — a genuinely useful default-behavior disclosure. It omits what happens when the ID doesn't exist (empty result vs error) and whether the record is permission-scoped.

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?

Two short sentences, zero preamble, with the core action front-loaded and the non-obvious custom-field rule immediately after. Nothing extraneous and nothing buried.

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?

For a two-parameter read tool whose annotations cover safety and whose schema fully documents inputs, the definition is serviceable, and no output schema means return-shape explanation isn't required. However, for a single-record fetch, the practical unknowns — default returned fields and not-found behavior — are left unaddressed.

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's fields guidance largely restates the schema's own enum-like explanation. It does emphasize the allFields/allCustom values in a more actionable place, which is a small gain, but no syntax, defaults, or interaction details are added beyond the schema.

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?

"Get one person by ID" gives a specific verb (get), a specific cardinality (one), and the lookup key (ID), which distinguishes it implicitly from listPeople and from getPersonByEmail. It stops short of naming that sibling explicitly, so an agent must infer the ID-vs-email split itself.

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 only implied: the "by ID" phrasing plus the sibling getPersonByEmail suggests when to pick each, but the description never states it, nor does it say when to prefer listPeople or checkDuplicate. No error-path or prerequisite guidance is given.

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