Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createRelationship

Create a new relationship contact, such as a spouse or partner, and link it to an existing person in Follow Up Boss.

Instructions

Create a relationship contact (own record, e.g. Spouse) linked to a person. It is not a link between two existing people.

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

Input Schema

NameRequiredDescriptionDefault
typeNoRelationship type, e.g. Spouse, Brother, Partner.
emailsNoEmails. First entry becomes primary. Each needs value.
phonesNoPhones. First entry becomes primary. Each needs value.
lastNameNoLast name.
personIdNoPerson this relationship belongs to.
addressesNoContact addresses (not property addresses).
firstNameNoFirst name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv2.0.0
    • changedInput schema / properties / addresses / description
      Previous value: -"Mailing addresses [{type, street, city, state, code, country}]"New value: +"Contact addresses (not property addresses)."
    • addedInput schema / properties / addresses / items / properties
      Added value: +{
      +  "city": {
      +    "description": "City",
      +    "type": "string"
      +  },
      +  "code": {
      +    "description": "ZIP code as string",
      +    "type": "string"
      +  },
      +  "country": {
      +    "description": "Country name",
      +    "type": "string"
      +  },
      +  "state": {
      +    "description": "2-letter state code",
      +    "type": "string"
      +  },
      +  "street": {
      +    "description": "Street",
      +    "type": "string"
      +  },
      +  "type": {
      +    "description": "home (default), work, mailing, investment",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / addresses / items / required
      Added value: +[]
    • changedInput schema / properties / emails / description
      Previous value: -"Email addresses [{type, value}]"New value: +"Emails. First entry becomes primary. Each needs value."
    • addedInput schema / properties / emails / items / properties
      Added value: +{
      +  "isPrimary": {
      +    "description": "Not needed; first entry is primary",
      +    "type": "boolean"
      +  },
      +  "type": {
      +    "description": "e.g. work, home",
      +    "type": "string"
      +  },
      +  "value": {
      +    "description": "Email address",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / emails / items / required
      Added value: +[
      +  "value"
      +]
    • changedInput schema / properties / firstName / description
      Previous value: -"First name of the relationship contact"New value: +"First name."
    • changedInput schema / properties / lastName / description
      Previous value: -"Last name of the relationship contact"New value: +"Last name."
    • changedInput schema / properties / personId / description
      Previous value: -"Person ID this relationship is associated with"New value: +"Person this relationship belongs to."
    • changedInput schema / properties / personId / type
      Previous value: -"number"New value: +"integer"
    • changedInput schema / properties / phones / description
      Previous value: -"Phone numbers [{type, value}]"New value: +"Phones. First entry becomes primary. Each needs value."
    • addedInput schema / properties / phones / items / properties
      Added value: +{
      +  "isPrimary": {
      +    "description": "Not needed; first entry is primary",
      +    "type": "boolean"
      +  },
      +  "type": {
      +    "description": "e.g. mobile, home, fax",
      +    "type": "string"
      +  },
      +  "value": {
      +    "description": "Phone number, e.g. 888-555-1234",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / phones / items / required
      Added value: +[
      +  "value"
      +]
    • changedInput schema / properties / type / description
      Previous value: -"Relationship type (e.g. Spouse, Brother, Partner)"New value: +"Relationship type, e.g. Spouse, Brother, Partner."
    • changedInput schema / required
      Previous value: -[
      -  "personId"
      -]New value: +[]
  2. Changed11 schema fields changedv1.1.3
    • addedInput schema / properties / addresses
      Added value: +{
      +  "description": "Mailing addresses [{type, street, city, state, code, country}]",
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / emails
      Added value: +{
      +  "description": "Email addresses [{type, value}]",
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / firstName
      Added value: +{
      +  "description": "First name of the relationship contact",
      +  "type": "string"
      +}
    • addedInput schema / properties / lastName
      Added value: +{
      +  "description": "Last name of the relationship contact",
      +  "type": "string"
      +}
    • removedInput schema / properties / notes
      Removed value: -{
      -  "description": "Notes about the relationship",
      -  "type": "string"
      -}
    • changedInput schema / properties / personId / description
      Previous value: -"First person ID"New value: +"Person ID this relationship is associated with"
    • addedInput schema / properties / phones
      Added value: +{
      +  "description": "Phone numbers [{type, value}]",
      +  "items": {
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • removedInput schema / properties / relatedPersonId
      Removed value: -{
      -  "description": "Related person ID",
      -  "type": "number"
      -}
    • removedInput schema / properties / relationshipType
      Removed value: -{
      -  "description": "Type of relationship",
      -  "type": "string"
      -}
    • addedInput schema / properties / type
      Added value: +{
      +  "description": "Relationship type (e.g. Spouse, Brother, Partner)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "personId",
      -  "relatedPersonId"
      -]New value: +[
      +  "personId"
      +]
  3. 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 the write profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false). The description adds the useful mental model that a new contact record is created, but says nothing about duplicate handling despite idempotentHint=false, nor about permissions, side effects, or what is returned. Useful but not rich beyond 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?

Two short sentences, the disambiguating clause placed second where it is most useful, with no filler or restatement of the name. Nothing could be removed without losing meaning.

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?

With seven all-optional parameters, a 100% documented schema and clear write annotations, the description covers the conceptual gap an agent would otherwise hit. One residual gap: it frames the record as "linked to a person" while personId is not required, leaving unclear whether an unlinked contact is valid.

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 every parameter including personId, type, emails and phones is already documented in the schema. The description's phrase "linked to a person" only lightly reinforces personId and adds nothing about type values or the first-entry-is-primary rule. Baseline 3 applies when the schema carries the parameter semantics.

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 ("Create a relationship contact") and immediately disambiguates the domain model: it is an own record (e.g. Spouse) attached to a person, not an edge between two people. That second sentence rules out the most likely misreading and separates it from sibling tools like createPerson and updateRelationship.

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?

Gives an explicit when-not ("not a link between two existing people") which is the main confusion risk for this tool. It does not name the alternative tool to use instead for linking two people, nor does it mention prerequisites such as which person fields must exist first, so it falls short of full alternative routing.

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