Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listAppointments

Read-onlyIdempotent

Retrieve appointments and filter them by person ID, user ID, or a start and end date range; supports pagination with limit, offset, and cursor.

Instructions

List appointments. Filter by personId (comma list allowed), userId, or a start+end date range (both required together).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listAppointments"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoRange end (date); must be used with start
nextNoCursor from _metadata.next of the previous call.
limitNoResults to return. FUB default 10, max 100.
startNoRange start (date); must be used with end
offsetNoRows to skip before results begin. Default 0.
userIdNoAppointments for this user ID
personIdNoPerson ID; comma-separated list allowed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv2.0.0
    • addedInput schema / properties / end
      Added value: +{
      +  "description": "Range end (date); must be used with start",
      +  "type": "string"
      +}
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results to return"New value: +"Results to return. FUB default 10, max 100."
    • changedInput schema / properties / next / description
      Previous value: -"Cursor for next page of results"New value: +"Cursor from _metadata.next of the previous call."
    • changedInput schema / properties / offset / description
      Previous value: -"Offset for pagination"New value: +"Rows to skip before results begin. Default 0."
    • changedInput schema / properties / personId / description
      Previous value: -"Filter by person"New value: +"Person ID; comma-separated list allowed"
    • changedInput schema / properties / personId / type
      Previous value: -"number"New value: +"string"
    • addedInput schema / properties / start
      Added value: +{
      +  "description": "Range start (date); must be used with end",
      +  "type": "string"
      +}
    • addedInput schema / properties / userId
      Added value: +{
      +  "description": "Appointments for this user ID",
      +  "type": "number"
      +}
  2. First observedv1.1.1

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds the start/end coupling rule but says nothing about pagination behavior, default result size, or ordering beyond what the schema already documents.

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?

Two sentences, front-loaded with the purpose and followed by the filter contract; nothing is wasted. It is slightly terse for a seven-parameter tool, but there is no filler.

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 a no-required-parameter list tool with full schema coverage and no output schema, this is close to sufficient. The one meaningful omission is what an unfiltered call returns, which an agent would need to know before invoking it with empty arguments.

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 each of the seven parameters is already documented in the schema, including the start/end pairing and the comma-list behavior for personId. The description largely restates those constraints rather than adding new semantics, so the baseline 3 applies.

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 opens with a specific verb+resource ('List appointments') and immediately characterizes the supported filtering dimensions. It implicitly distinguishes the tool from getAppointment/listAppointmentTypes by framing it as a filtered collection read, though it never names a sibling explicitly.

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?

It gives real filtering guidance, including the important constraint that start and end must be supplied together, and notes personId accepts a comma list. However, there is no when-to-use vs. when-not guidance, no statement about what happens with no filters, and no pointer to alternatives such as getAppointment for single-record retrieval.

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