Skip to main content
Glama

get_appointment

Read-onlyIdempotent

Read a booking and its current revision by ID in the approved workspace. Share reviewUrl so the owner can review and approve a booking request in Cockatoo. Times are Unix milliseconds. Recorded payment amounts use minor units in the payment currency.

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and closed-world, so the safety profile is covered. The description adds genuinely new context beyond that: the record is resolved within 'the approved workspace', the returned reviewUrl is meant to be shared with the owner for approval, and timestamp/payment units are disclosed. It does not say what happens when the ID is unknown or unapproved.

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?

Four short sentences with the core action front-loaded, followed by consumer-facing context and then unit conventions. Tight and information-dense; the imperative "Share reviewUrl so the owner can review" leans toward workflow instruction rather than tool description, a minor blemish.

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?

With no output schema, the description does the right thing by previewing key return semantics (reviewUrl, Unix-millisecond times, minor-unit payment amounts) for a one-parameter read. For a simple read tool this is close to sufficient; only error/permission behavior and the meaning of 'current revision' are left unstated.

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 0% for the single required parameter, so the description must carry the load. "by ID" establishes that the argument is a booking identifier, but it does not specify whether this is the appointment ID versus a change/revision ID, nor any format expectations beyond the schema's 1-128 character bounds.

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?

"Read a booking and its current revision by ID" gives a specific verb (read), a resource (booking), and a scope qualifier (by ID, plus "current revision") that separates it from the list_* siblings. It does not explicitly name an alternative or say that it is the single-record counterpart to the list tools, so it stops short of a 5.

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?

Usage is only implied: "by ID" tells the agent this is the single-record lookup, and "in the approved workspace" hints at a scoping constraint, but the description never states when to prefer this over list_appointment_changes or the get_appointment_* sub-resource tools. No exclusions or prerequisites (permissions, not-found behavior) are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources