Skip to main content
Glama
gray-wilbee

fub-mcp

by gray-wilbee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

update_appointment

Update an existing appointment's details such as title, start/end times, location, and invitees in Follow Up Boss CRM.

Instructions

Update an appointment. (PUT /appointments/{id})

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
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.
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.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only conveys that the operation updates, but does not explain whether unspecified fields are reset, whether invitations are sent, what side effects occur, or what response to expect. This is a significant gap for a mutating endpoint.

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

Conciseness4/5

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

The description is one short sentence plus the endpoint, with no filler. It is front-loaded and economical, though the brevity contributes to missing behavioral and usage context.

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?

This is a 13-parameter mutation tool with no annotations and no output schema, yet the description provides almost no additional context beyond the schema. An agent still lacks clarity on update semantics, return values, side effects, and how this endpoint relates to the many sibling appointment and event tools.

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 92%, so the parameters are already well documented in the schema. The description adds only the {id} path context, which is useful but minimal; most parameter meaning is carried by the input schema.

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 states a clear action ('Update') and resource ('an appointment'), and includes the HTTP method and path (PUT /appointments/{id}). It does not explicitly contrast itself with sibling tools like create_appointment or update_appointment_type, so it misses the differentiator needed for 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 Guidelines2/5

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

There is no guidance about when to use this tool versus alternatives such as create_appointment or get_appointment. The endpoint path implies the resource, but the description does not state prerequisites, whether an existing appointment id is required, or when another tool should be preferred.

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