Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listRelationships

Read-onlyIdempotent

Retrieve relationship contacts such as spouses or partners, with optional filters by person ID or fuzzy name. Use it to find linked contacts in Follow Up Boss CRM.

Instructions

List relationship contacts (spouse, partner, etc.), optionally for one person or by name.

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

Input Schema

NameRequiredDescriptionDefault
nameNoFuzzy name match.
nextNoCursor from _metadata.next of the previous page.
sortNoSort field.
limitNoResults per call. Default 10, max 100.
offsetNoRows to skip. Default 0. Prefer next for deep paging.
lastNameNoFuzzy last-name match.
personIdNoOnly relationships of this person.
firstNameNoFuzzy first-name match.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv2.0.0
    • addedInput schema / properties / firstName
      Added value: +{
      +  "description": "Fuzzy first-name match.",
      +  "type": "string"
      +}
    • addedInput schema / properties / lastName
      Added value: +{
      +  "description": "Fuzzy last-name match.",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"Results per call. Default 10, max 100."
    • changedInput schema / properties / limit / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / name
      Added value: +{
      +  "description": "Fuzzy name match.",
      +  "type": "string"
      +}
    • addedInput schema / properties / next
      Added value: +{
      +  "description": "Cursor from _metadata.next of the previous page.",
      +  "type": "string"
      +}
    • changedInput schema / properties / offset / description
      Previous value: -"Offset for pagination"New value: +"Rows to skip. Default 0. Prefer next for deep paging."
    • changedInput schema / properties / offset / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / personId / description
      Previous value: -"Person ID"New value: +"Only relationships of this person."
    • changedInput schema / properties / personId / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Sort field.",
      +  "enum": [
      +    "id",
      +    "created",
      +    "updated",
      +    "name",
      +    "firstName",
      +    "lastName",
      +    "personId"
      +  ],
      +  "type": "string"
      +}
  2. 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 readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds only the notion of relationship contacts; it says nothing about pagination behavior (cursor vs offset) or result shape, which would be the genuinely additive context here.

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 compact sentence with no redundant wording, and the core purpose is front-loaded before the optional filtering clause. 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.

Completeness3/5

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

With eight optional parameters, full schema coverage, and complete annotations, the minimum needed to call the tool is present. However, for a paginated list tool with no output schema, the description omits any mention of paging or return ordering, leaving a real gap.

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%, so the schema documents all eight parameters including fuzzy matching, sort fields, and cursor paging. The description only loosely maps 'for one person' to personId and 'by name' to the name fields, adding marginal meaning. Baseline 3 applies when the schema does the heavy lifting.

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 ('List relationship contacts') and clarifies the resource with examples ('spouse, partner, etc.'). It does not differentiate from siblings like getRelationship or listPeople, which is the only thing keeping it from a 5.

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?

'Optionally for one person or by name' implies two filtering modes, so an agent can infer usage, but there is no explicit when-to-use versus getRelationship/listPeople and no statement of exclusions. Guidance is implied rather than stated.

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