Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getAppointment

Read-onlyIdempotent

Retrieve a specific appointment by its ID from Follow Up Boss CRM to view scheduling details and related contact information.

Instructions

Get an appointment by ID

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": {
      "id": "<id>"
    },
    "name": "getAppointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAppointment ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that: no note on what happens with an unknown ID, no mention of auth or rate behavior, and no return-shape detail despite there being no output schema.

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?

One short sentence, front-loaded with the verb and with zero filler or repetition. It is efficient, though the brevity borders on under-specification rather than true conciseness.

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 single-parameter read tool this is minimally adequate, but with no output schema the description should say something about what an appointment record contains or what occurs on a missing ID. As written, the agent has enough to invoke it but not enough to interpret the result confidently.

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?

There is a single required parameter with 100% schema description coverage ('Appointment ID'), so the schema does the heavy lifting. The description's 'by ID' phrasing matches and adds no further meaning, which is the expected baseline when coverage is complete.

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 states a specific verb and resource ('Get an appointment') plus the lookup key ('by ID'), so an agent knows exactly what the tool returns a single record of. It does not, however, distinguish itself from the sibling listAppointments, createAppointment, or updateAppointment beyond the verb itself.

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?

There is no explicit when-to-use guidance: nothing says to call this only when a single appointment ID is known, or to use listAppointments for enumeration. The 'by ID' phrase implies single-record retrieval, but the agent must infer it.

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