Skip to main content
Glama

complete_appointment

Idempotent

Mark a confirmed appointment that has started as complete using its current revision. This can queue a customer review email if the business has enabled review requests.

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>",
      "revision": "<revision>"
    },
    "name": "complete_appointment"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare this is a non-destructive, idempotent, open-world write, so the description doesn't need to restate the safety profile. What it does add is genuinely useful: a hidden side effect (it may queue a customer review email when review requests are enabled) and a concurrency requirement ('using its current revision'). It leaves out the failure mode when the revision is stale, which would be the last piece.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tight sentences with the precondition front-loaded first and the side effect second. No filler, no repetition of the tool name, and every clause carries information the agent needs.

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?

For a two-parameter mutation with no output schema, the definition covers the key preconditions and the one non-obvious consequence (review email queuing). It is slightly incomplete on what the call returns and what happens when the revision is out of date, but nothing essential to deciding whether to invoke it is missing.

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%, so both parameters depend on the description for meaning. 'Its current revision' hints that revision is an optimistic-concurrency token that must match the stored value, and 'a confirmed appointment' implies id identifies which appointment. That is partial compensation; the uuid format of id and the concept of a revision mismatch error are left for the agent to infer.

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 uses a specific verb and resource ('Mark a ... appointment ... as complete') and narrows the target with two preconditions: the appointment must be confirmed and must have started. That is far more precise than a bare 'complete appointment', and it distinguishes it from confirm_appointment and cancel_appointment by outcome, though it does not name any sibling explicitly.

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?

The phrase 'a confirmed appointment that has started' gives an implicit when-to-use rule an agent can check before calling. It stops short of stating when not to use it or which sibling to reach for instead (for example, cancel_appointment or mark_appointment_no_show for other terminal states), so the guidance is implied rather than spelled out.

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