Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

createAppointment

Schedule an appointment with start and end times, optional type, location, description, and invitees; optionally send email or SMS invitations to users or contacts.

Instructions

Create an appointment. Use start/end (UTC; offset suffix allowed), typeId/outcomeId, invitees [{userId}] or [{personId}]. sendInvitation=true emails invitees (SMS too if reminders are on); default false.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "title": "<title>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "createAppointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesEnd, ISO 8601 UTC or with offset
startYesStart, ISO 8601 UTC or with offset
titleYesAppointment title
allDayNoAll-day event. Default false
typeIdNoAppointment type ID (see listAppointmentTypes)
inviteesNoPeople/users to invite: [{userId}] for a user, [{personId}] for a contact (optional name, email).
locationNoLocation or address
outcomeIdNoAppointment outcome ID (see listAppointmentOutcomes)
createdByIdNoCreator user ID; admins only
descriptionNoDescription
sendInvitationNoQuery param: email invitees. Default false

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv2.0.0
    • addedInput schema / properties / allDay / description
      Added value: +"All-day event. Default false"
    • changedInput schema / properties / createdById / description
      Previous value: -"Creator user ID (admin only)"New value: +"Creator user ID; admins only"
    • changedInput schema / properties / end / description
      Previous value: -"End ISO 8601 (required)"New value: +"End, ISO 8601 UTC or with offset"
    • changedInput schema / properties / invitees / description
      Previous value: -"Array of {type:'person'|'user', id:int}"New value: +"People/users to invite: [{userId}] for a user, [{personId}] for a contact (optional name, email)."
    • addedInput schema / properties / invitees / items / properties
      Added value: +{
      +  "email": {
      +    "description": "Email (people)",
      +    "type": "string"
      +  },
      +  "name": {
      +    "description": "Display name",
      +    "type": "string"
      +  },
      +  "personId": {
      +    "description": "FUB person ID",
      +    "type": "number"
      +  },
      +  "userId": {
      +    "description": "FUB user ID",
      +    "type": "number"
      +  }
      +}
    • changedInput schema / properties / location / description
      Previous value: -"Location"New value: +"Location or address"
    • changedInput schema / properties / outcomeId / description
      Previous value: -"Appointment outcome ID"New value: +"Appointment outcome ID (see listAppointmentOutcomes)"
    • addedInput schema / properties / sendInvitation
      Added value: +{
      +  "description": "Query param: email invitees. Default false",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / start / description
      Previous value: -"Start ISO 8601 (required)"New value: +"Start, ISO 8601 UTC or with offset"
    • changedInput schema / properties / title / description
      Previous value: -"Appointment title (required)"New value: +"Appointment title"
    • changedInput schema / properties / typeId / description
      Previous value: -"Appointment type ID"New value: +"Appointment type ID (see listAppointmentTypes)"
  2. 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"
      +]
  3. First observedv1.1.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only say readOnly=false, destructive=false, idempotent=false, openWorld=false — nothing about side effects. The description adds genuinely new behaviour: sendInvitation=true emails invitees, additionally sends SMS when reminders are enabled, and defaults to false. That side-effect and default disclosure is exactly what an agent needs before mutating. It omits whether repeat calls duplicate appointments (relevant given idempotentHint=false) and what the response returns.

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?

Three tight sentences, front-loaded with the action, then format constraints, then the invitation side effect. Telegraphic style ('invitees [{userId}] or [{personId}]') is efficient but slightly cryptic in isolation; still, every clause carries information and nothing is padding.

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

Completeness4/5

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

For an 11-parameter mutation tool with no output schema, the definition covers the risky parts: date format/timezone, reference IDs, invitee shape, and the notification side effect and its default. Missing pieces are minor — timezone default when no offset is given, duplicate/conflict behaviour, and what is returned on success.

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 baseline is 3. The description reinforces the two invitee shapes ([{userId}] or [{personId}]) and the offset-suffix allowance on start/end, but this largely restates what the schema already documents, and the remaining parameters (allDay, location, createdById, description) get no mention beyond the 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?

Opens with a specific verb+resource: 'Create an appointment.' That distinguishes it from listAppointments/getAppointment/updateAppointment, and the appointment-type/outcome siblings are distinguishable by the description's focus on creating an appointment instance. It stops short of explicitly naming those near-neighbours (createAppointmentType, createAppointmentOutcome), so not 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 Guidelines3/5

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

Usage is implied by the verb — you call it when you need a new appointment — and it hints at the referenced lookups (typeId/outcomeId resolve via listAppointmentTypes/listAppointmentOutcomes in the schema). There is no explicit when-to-use vs. alternatives guidance and no when-not or prerequisite statement (e.g., must the invitee person already exist?).

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