Skip to main content
Glama
mindwear-capitian

followupboss-mcp-server

by mindwear-capitian
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

updateAppointment

Update appointment details such as title, time, location, and invitees. Provide both start and end values on every update to prevent 'Valid Start and End dates are required' errors.

Instructions

Update an appointment. FUB requires start and end on EVERY update (even partial edits) or it returns 'Valid Start and End dates are required'. Refetch with getAppointment first if you only have the id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesAppointment ID
endNoEnd ISO
startNoStart ISO
titleNo
allDayNo
typeIdNoType ID
inviteesNo
locationNo
outcomeIdNoOutcome ID
descriptionNo

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": "Type ID",
-  "type": "number"
-}
    • removedInput schema / properties / description / description
      Removed value: -"Description"
    • addedInput schema / properties / end
      Added value: +{
+  "description": "End ISO",
+  "type": "string"
+}
    • removedInput schema / properties / endTime
      Removed value: -{
-  "description": "End time",
-  "type": "string"
-}
    • removedInput schema / properties / invitees / description
      Removed value: -"Invitees"
    • removedInput schema / properties / location / description
      Removed value: -"Location"
    • addedInput schema / properties / outcomeId
      Added value: +{
+  "description": "Outcome ID",
+  "type": "number"
+}
    • removedInput schema / properties / personId
      Removed value: -{
-  "description": "Person ID",
-  "type": "number"
-}
    • addedInput schema / properties / start
      Added value: +{
+  "description": "Start ISO",
+  "type": "string"
+}
    • removedInput schema / properties / startTime
      Removed value: -{
-  "description": "Start time",
-  "type": "string"
-}
    • removedInput schema / properties / title / description
      Removed value: -"Title"
    • addedInput schema / properties / typeId
      Added value: +{
+  "description": "Type ID",
+  "type": "number"
+}
  2. First observedv1.1.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description reveals a critical behavioral constraint: the API returns an error unless both start and end are supplied on every update. This goes beyond the schema requirements and informs the agent of a non-obvious failure mode, though other behaviors like permissions or idempotency are not covered.

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?

Two concise sentences: the first states the core purpose, the second provides critical behavioral guidance. Every sentence adds value with no redundancy, making it easy for the agent to parse and act on.

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?

Given 10 parameters, a non-obvious API requirement (start/end mandatory on all updates), and no output schema, the description is fairly complete. It alerts the agent to a common error and suggests a remedial action (refetch with getAppointment). Missing details like response format or other constraints, but overall sufficient for correct invocation.

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 description coverage is 50% (5 of 10 parameters have descriptions). The description adds significant semantic context by highlighting that start and end are effectively required despite not being in the schema's required list, and by recommending a workflow to obtain those values. This compensates for the schema's lack of completeness on these critical parameters.

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 'Update an appointment.' as the verb+resource pair, and the additional context about FUB requiring start/end on every update distinguishes it from a typical partial-update tool, making the purpose unambiguous.

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

Usage Guidelines4/5

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

Explicitly advises to refetch with getAppointment if only the id is available, and notes that start and end are required on every update. This provides definite usage context, though it does not discuss alternatives for other scenarios beyond the immediate requirement.

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