Skip to main content
Glama

confirm_appointment

Confirm a pending booking using its current revision. Obtain owner approval for the booking first. This records a confirmation. Use the review link to email it from Cockatoo.

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

Input Schema

NameRequiredDescriptionDefault
idYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive mutation, and the description adds useful context: a mandatory owner-approval prerequisite and that the call 'records a confirmation'. The 'current revision' phrasing hints at optimistic-concurrency failure on stale revisions, but this is left implicit and nothing is said about what happens to the booking state or what errors result.

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, front-loaded with the action and the key precondition; nothing is padded. The closing sentence about the review link is somewhat ambiguous in wording and 'This records a confirmation' partly restates the verb.

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 two-parameter mutation with no output schema and zero schema coverage, the description covers the action and prerequisite but leaves the revision parameter's origin, failure modes, and resulting state unspecified. It is adequate to attempt the call but not to anticipate its behavior.

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 0%, so both parameters are undocumented structurally, and the description only implies that 'id' identifies the booking and 'revision' is a concurrency token that must be current. It does not explain where the revision value comes from or what happens if it is stale, so it partially but not fully compensates for the coverage gap.

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?

States a specific verb and resource: 'Confirm a pending booking', scoped to pending bookings and requiring the booking's current revision. It is distinguishable from siblings such as cancel_appointment and complete_appointment by the word 'confirm', though it never names those alternatives 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?

Gives a real precondition ('Obtain owner approval for the booking first') and a follow-on action (email via the review link), which implies context of use. It does not state when not to use it, nor does it name an alternative tool for bookings that are not pending.

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