Skip to main content
Glama
followupboss-mcp-server

followupboss-mcp-server

getAppointmentType

Read-onlyIdempotent

Retrieves an appointment type by its ID, returning its details for scheduling and CRM reference.

Instructions

Get appointment type 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": "getAppointmentType"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesType 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 without description help. The description adds nothing beyond that: no statement about what is returned, what happens on a missing/invalid ID, or whether results are cached or scoped. With annotations carrying the entire behavioral load, this is a missed opportunity rather than a contradiction.

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 with no redundant wording, and the key constraint (by ID) is front-loaded. It is minimally sized rather than padded, though it borders on under-specified given the sparse content.

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 single-parameter read with four annotations, full schema coverage, and no output schema, the definition is adequate but thin. An agent still lacks any hint about the return shape or not-found behavior, which would be the remaining useful additions.

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%, and the single parameter is documented as 'Type ID' with the required flag. The description's 'by ID' merely echoes the parameter without adding format, source, or validation detail, 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 states a specific verb (Get) and resource (appointment type) plus the lookup key (by ID), which is enough for an agent to know it retrieves a single entity. It does not explicitly distinguish itself from the adjacent listAppointmentTypes or getAppointment, relying on the reader to infer single-record retrieval from 'by ID'.

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 use this versus listAppointmentTypes or getAppointment, and no mention of prerequisites or error behavior when the ID does not exist. The only implied usage is the single-record lookup, which comes from the phrase 'by ID' rather than any explicit instruction.

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