Skip to main content
Glama
mindwear-capitian

followupboss-mcp-server

by mindwear-capitian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

createRelationship

Create a new contact record for a relationship (spouse, partner, etc.) linked to an existing person in Follow Up Boss, with optional details like name, emails, phones, and addresses.

Instructions

Create a relationship contact (Spouse, Brother, Partner, etc.) for an existing person. The relationship is its own contact record linked to personId — it is NOT a link between two existing people.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoRelationship type (e.g. Spouse, Brother, Partner)
emailsNoEmail addresses [{type, value}]
phonesNoPhone numbers [{type, value}]
lastNameNoLast name of the relationship contact
personIdYesPerson ID this relationship is associated with
addressesNoMailing addresses [{type, street, city, state, code, country}]
firstNameNoFirst name of the relationship contact

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. First observedv1.1.1

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided; description fails to disclose any behavioral traits such as side effects, required permissions, or error conditions. The description only states the basic function.

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 sentences, no redundancy, front-loaded with key insight. Every word earns its place.

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?

Provides core functionality but lacks details on return values (no output schema), validation rules, or default behavior. Acceptable for a simple create tool but not fully complete.

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 already documents all parameters. The description adds minimal extra meaning beyond confirming the relationship is a separate record linked to personId. Baseline 3 is appropriate.

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?

Description clearly states it creates a relationship contact (Spouse, Brother, etc.) for an existing person and distinguishes it from linking two existing people, making purpose unambiguous.

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?

Purpose is clear but no explicit when-to-use or when-not-to-use guidance. Implicitly, it's for creating new relationship records, but does not contrast with other create tools like createPerson or updateRelationship.

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