Skip to main content
Glama
gray-wilbee

fub-mcp

by gray-wilbee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_appointment

Schedule appointments in Follow Up Boss by specifying title, start/end times, invitees, location, and optional reminders.

Instructions

Create an appointment. (POST /appointments)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesThe ending date and time of the appointment (in UTC, also supports time zone suffix).
startYesThe beginning date and time of the appointment (in UTC, also supports time zone suffix).
titleYesTitle of the appointment.
allDayNoSets whether the appointment is an all day event or not.
typeIdNoThe Follow Up Boss appointment type identifier.
inviteesNoArray of users and/or people to invite to the appointment. (e.g., User object: `{userId: 1, name: "Tom Minch"}`, People object: `{personId: "123", name: "John Q Customer", email: "johnq@example.com"}`)
locationNoThe location or address of the appointment.
extraBodyNoExtra raw JSON body fields not explicitly listed above — e.g. custom.* fields when creating/updating people or deals. Keys and values are sent as-is.
outcomeIdNoThe Follow Up Boss appointment outcome identifier.
extraQueryNoExtra raw query parameters not explicitly listed above — e.g. FUB custom field filters like custom.ClosingDate on /people or /deals. Keys and values are sent as-is.
createdByIdNoThe id of the user that created the appointment. (Note: This can only be set by admins, otherwise the currently logged in user's ID is used.)
descriptionNoDescription of the appointment or event.
sendInvitationNoSend an invitation email to invitees. (Note: If the "appointment reminders" is enabled, an SMS reminder will also be sent.)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.4/5.0
Behavior1/5

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

With no annotations, the description must carry the full burden of behavioral disclosure. It only states 'Create an appointment' and the endpoint, adding nothing about side effects (e.g., sending invitations, admin-only fields), authentication, or response behavior. The schema descriptions for parameters like sendInvitation and createdById carry the behavioral hints, not the tool description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise, but it is essentially a restatement of the tool name and endpoint. It does not front-load any unique value or earn its place; it is minimal to the point of being uninformative.

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

Completeness1/5

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

For a tool with 13 parameters, nested objects, and no output schema, the description is severely incomplete. It lacks any mention of return values, error conditions, required context (like timezone handling), or admin restrictions. The schema and sibling names provide more context than the description itself.

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?

The schema covers 100% of parameters with detailed descriptions, so the baseline is 3. The tool description adds no parameter-level meaning beyond what the schema already provides, so it neither improves nor degrades the baseline.

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 and resource: 'Create an appointment.' This is specific and distinguishes it from read-only tools like get_appointment or list_appointments. However, it does not differentiate from sibling create tools like create_event, which also creates an appointment-like entity, so it lacks explicit sibling differentiation.

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 gives no guidance on when to use this tool versus alternatives. It does not mention any conditions, exclusions, or when to prefer create_event or update_appointment. The only clue is the HTTP method, which is not usage guidance.

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