Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getAppointmentOutcome

Read-onlyIdempotent

Fetch an appointment outcome by its ID to review the result details for a specific Follow Up Boss appointment.

Instructions

Get appointment outcome 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": "getAppointmentOutcome"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOutcome 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?

Annotations already declare readOnlyHint, idempotentHint, 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 for an unknown ID (e.g., error vs null) or any return characteristics.

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?

A single short sentence with no wasted words and the essential scoping phrase front-loaded. It is efficient, though its brevity borders on under-specification rather than tightness.

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

Completeness2/5

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

There is no output schema, so the description carries the burden of explaining what an 'outcome' record actually contains, and it does not. For a fetch-by-ID tool in a large sibling set, that omission leaves the agent unable to predict the response shape.

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 coverage is 100% and the single required parameter is documented as 'Outcome ID'. The description repeats that same meaning with no additional detail such as ID format or provenance, so the baseline 3 for schema-covered parameters 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 states a specific verb ('Get') and resource ('appointment outcome'), with the keying mechanism ('by ID') made explicit. It is clearly distinct from write siblings like createAppointmentOutcome/updateAppointmentOutcome, but it never names listAppointmentOutcomes or explains how a single fetch differs from the list operation.

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 guidance on when to call this rather than listAppointmentOutcomes or updateAppointmentOutcome. The only hint is the implicit 'by ID' vs listing distinction, which the agent must infer entirely on its own.

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