Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

listAppointmentOutcomes

Read-onlyIdempotent

Retrieves available appointment outcomes from Follow Up Boss, sorted by orderWeight by default. Use it to populate outcome options or paginate through results with limit, offset, and cursor controls.

Instructions

List appointment outcomes. Default sort is orderWeight.

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": "listAppointmentOutcomes"
  }
}

Input Schema

NameRequiredDescriptionDefault
nextNoCursor from _metadata.next of the previous call.
sortNoSort field; '-' prefix = descending. Default orderWeight
limitNoResults to return. FUB default 10, max 100.
offsetNoRows to skip before results begin. Default 0.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv2.0.0
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Results to return. FUB default 10, max 100.",
      +  "type": "number"
      +}
    • addedInput schema / properties / next
      Added value: +{
      +  "description": "Cursor from _metadata.next of the previous call.",
      +  "type": "string"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip before results begin. Default 0.",
      +  "type": "number"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Sort field; '-' prefix = descending. Default orderWeight",
      +  "enum": [
      +    "id",
      +    "name",
      +    "orderWeight",
      +    "-id",
      +    "-name",
      +    "-orderWeight"
      +  ],
      +  "type": "string"
      +}
  2. First observedv1.1.1

TDQS

B3.2/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 covered and this description does not contradict it. The only added behavior is the default sort order, which is marginal and partly duplicated by the sort parameter's own default note; no mention of pagination flow despite the cursor-based next parameter.

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 short sentences, front-loaded with the purpose and containing no wasted wording. The second sentence is largely redundant with the schema default, which keeps it from a 5.

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

Completeness3/5

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

For a simple read-only list tool with full schema coverage and four annotations, the description is adequate but thin: it omits the cursor-based pagination flow across the next parameter and gives no hint about the result shape or empty results. It is minimum viable rather than complete.

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 next, sort, limit and offset are already fully documented by the schema, including the enum values and defaults. The description adds only the default sort restatement, which the schema already carries, so 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?

States a specific verb+resource ("List appointment outcomes"), which clearly distinguishes it from createAppointmentOutcome, getAppointmentOutcome and updateAppointmentOutcome among the siblings. It stops short of naming the sibling list tools or describing what the returned objects contain, so it is clear but not fully differentiating.

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?

No when-to-use guidance and no exclusions or prerequisites. An agent must infer that this is the enumeration counterpart to getAppointmentOutcome purely from the name, and nothing tells it whether this should be preferred over fetching individual outcomes.

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