Skip to main content
Glama
mindwear-capitian

followupboss-mcp-server

createPerson

Add new contacts to Follow Up Boss CRM with details like name, contact info, pipeline stage, and lead source to organize customer relationships.

Instructions

Create a new person/contact in FUB

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
deduplicateNoCheck for duplicates before creating (query param)
createdAtNoISO timestamp for creation date
firstNameNoFirst name
lastNameNoLast name
stageNoPipeline stage
sourceNoLead source
sourceUrlNoSource URL
contactedNoWhether person has been contacted
priceNoPrice point
assignedToNoAssigned agent name
assignedUserIdNoAssigned user ID
assignedPondIdNoAssigned pond ID
assignedLenderNameNoAssigned lender name
assignedLenderIdNoAssigned lender ID
emailsNoEmail addresses: [{value, type}]
phonesNoPhone numbers: [{value, type}]
addressesNoAddresses: [{street, city, state, code, type}]
tagsNoTags to apply
backgroundNoBackground info
collaboratorsNoCollaborator user IDs
timeframeIdNoTimeframe ID
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states it creates a new person/contact, implying a write operation, but lacks critical details such as permissions needed, whether it's idempotent, error handling, or response format. This leaves significant gaps in understanding the tool's behavior.

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?

The description is a single, efficient sentence with zero wasted words. It is front-loaded with the core action and resource, making it highly concise and well-structured for quick comprehension.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

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

Given the complexity (21 parameters, no required fields, no output schema, and no annotations), the description is inadequate. It does not explain return values, error conditions, or behavioral nuances, leaving the agent poorly equipped to use this mutation tool effectively in context.

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 fully documents all 21 parameters. The description adds no additional semantic context about parameters, such as which are required or typical usage patterns. Baseline score of 3 is appropriate as the schema handles 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 clearly states the verb ('Create') and resource ('a new person/contact in FUB'), making the purpose unambiguous. However, it does not differentiate from sibling tools like 'updatePerson' or 'bulkUpdatePeople', which would require specifying it's for initial creation only.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., required fields), exclusions, or comparisons to siblings like 'updatePerson' or 'checkDuplicate', leaving the agent without contextual usage instructions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mindwear-capitian/followupboss-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server