Skip to main content
Glama

Rudko — vertebrologist (Chernivtsi, Ukraine)

cancel

Idempotent

Cancels the user's appointment by booking_id, as returned by list_current_bookings. Returns ok=true with cancelled set to that booking_id, or ok=false with a reason: not_found (no such appointment for this user) or bad_id (not a valid UUID). A cancellation is reversible — the freed slot can be booked again — which is why this tool is not marked destructive. To change the time instead of giving the appointment up, reschedule moves it atomically within the same day. Authorization required: the one-time Telegram OAuth consent (scope booking:write), which also covers later calls.

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": {
      "booking_id": "<booking_id>"
    },
    "name": "cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
booking_idYesUUID of the appointment, exactly as list_current_bookings returned it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / booking_id / description
      Added value: +"UUID of the appointment, exactly as list_current_bookings returned it."
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes beyond the annotations by explaining the reversibility rationale behind destructiveHint=false, enumerating both failure modes (not_found, bad_id) with their meanings, and disclosing the OAuth scope (booking:write) plus the fact that consent persists for later calls. It does not describe concurrent-cancellation behavior or what happens if the slot is rebooked between calls, so it stops just short of fully exhaustive.

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?

Front-loaded with the action, then return shape, then failure codes, then the reschedule alternative and auth — a sensible ordering with no filler. The trailing clause about consent also covering later calls is marginally tangential to invoking this tool, keeping it off a 5.

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

Completeness5/5

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

For a one-parameter mutation with a known-good annotation set and no output schema, the definition covers success shape (ok=true with cancelled), failure shape (ok=false with reason), reversibility, prerequisites, and the sibling alternative. Nothing an agent needs in order to call it correctly 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 coverage is 100%, so the single parameter is already documented in the schema. The description reinforces the source of the UUID ("as returned by list_current_bookings") and ties it to the bad_id error, but adds no syntax or format detail the schema does not already carry. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource pair ("Cancels the user's appointment") plus the exact key it operates on (booking_id, sourced from list_current_bookings). An agent can distinguish it immediately from reschedule (which moves the appointment) and from the list tools without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use (give the appointment up) and names the alternative with the condition that selects it: "To change the time instead of giving the appointment up, reschedule moves it atomically within the same day." It also tells the agent where the required identifier comes from, closing the pre-call loop.

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