Skip to main content
Glama
mindwear-capitian

followupboss-mcp-server

by mindwear-capitian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

createAppointment

Schedule a new appointment in Follow Up Boss by providing a title, start and end times, and optional details like location, invitees, or appointment type.

Instructions

Create an appointment. FUB uses start/end (not startTime/endTime), typeId/outcomeId (not appointmentTypeId/appointmentOutcomeId), and invitees:[{type:'person'|'user',id}] (personId is NOT a top-level field).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endYesEnd ISO 8601 (required)
startYesStart ISO 8601 (required)
titleYesAppointment title (required)
allDayNo
typeIdNoAppointment type ID
inviteesNoArray of {type:'person'|'user', id:int}
locationNoLocation
outcomeIdNoAppointment outcome ID
createdByIdNoCreator user ID (admin only)
descriptionNoDescription

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv1.1.3
    • addedInput schema / properties / allDay
      Added value: +{
+  "type": "boolean"
+}
    • removedInput schema / properties / appointmentOutcomeId
      Removed value: -{
-  "description": "Outcome ID",
-  "type": "number"
-}
    • removedInput schema / properties / appointmentTypeId
      Removed value: -{
-  "description": "Appointment type ID",
-  "type": "number"
-}
    • addedInput schema / properties / createdById
      Added value: +{
+  "description": "Creator user ID (admin only)",
+  "type": "number"
+}
    • addedInput schema / properties / end
      Added value: +{
+  "description": "End ISO 8601 (required)",
+  "type": "string"
+}
    • removedInput schema / properties / endTime
      Removed value: -{
-  "description": "End time ISO",
-  "type": "string"
-}
    • changedInput schema / properties / invitees / description
      Previous value: -"Invitees"New value: +"Array of {type:'person'|'user', id:int}"
    • addedInput schema / properties / outcomeId
      Added value: +{
+  "description": "Appointment outcome ID",
+  "type": "number"
+}
    • removedInput schema / properties / personId
      Removed value: -{
-  "description": "Person ID",
-  "type": "number"
-}
    • addedInput schema / properties / start
      Added value: +{
+  "description": "Start ISO 8601 (required)",
+  "type": "string"
+}
    • removedInput schema / properties / startTime
      Removed value: -{
-  "description": "Start time ISO",
-  "type": "string"
-}
    • changedInput schema / properties / title / description
      Previous value: -"Appointment title"New value: +"Appointment title (required)"
    • addedInput schema / properties / typeId
      Added value: +{
+  "description": "Appointment type ID",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[]New value: +[
+  "title",
+  "start",
+  "end"
+]
  2. First observedv1.1.1

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It states creation but omits side effects, permissions (e.g., admin-only field), success/failure behavior, or what is returned. This is insufficient for an agent to understand the tool's full impact.

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 sentence that efficiently communicates the purpose and key naming caveats. No extraneous words, and the critical information is front-loaded.

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?

Despite high schema coverage, the description lacks completeness for a creation tool with 10 parameters. It doesn't explain return values, required scopes, or how it fits among siblings. The naming hints are helpful but insufficient for full contextual understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is high (90%), giving a baseline of 3. The description adds value by clarifying naming conventions (start/end instead of startTime/endTime), the invitees structure, and warning that personId is not top-level. This goes beyond the schema's descriptions.

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?

The description clearly states 'Create an appointment' as a specific action on a resource. It distinguishes from siblings by highlighting naming conventions unique to FUB, which helps avoid confusion with similar tools like updateAppointment or createAppointmentOutcome.

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 (e.g., updateAppointment). It does not mention any prerequisites, context, or exclusions, leaving the agent to infer usage solely from the verb 'Create'.

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