Skip to main content
Glama

Rudko — vertebrologist (Chernivtsi, Ukraine)

book

Creates a real appointment with the vertebrologist on the user's behalf. Takes date (YYYY-MM-DD) and time (HH:MM), both required; the slot must be one returned by get_availability. Returns ok=true with the booked date and time, or ok=false with a reason: taken (the slot is no longer free; the call fails rather than quietly moving the user to a different time), day_limit (this patient already has an appointment that day — the limit is one per calendar day), locked (the doctor closed that day or slot), past, invalid, error. Authorization required: a one-time Telegram OAuth consent with 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": {
      "date": "<date>",
      "time": "<time>"
    },
    "name": "book"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesAppointment date, YYYY-MM-DD (Europe/Kyiv). Must be a day returned by get_availability.
timeYesSlot start, HH:MM in 24-hour form, exactly as get_availability returned it. Slots are 20 minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / date / description
      Added value: +"Appointment date, YYYY-MM-DD (Europe/Kyiv). Must be a day returned by get_availability."
    • addedInput schema / properties / time / description
      Added value: +"Slot start, HH:MM in 24-hour form, exactly as get_availability returned it. Slots are 20 minutes."
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

The description adds substantial behavior beyond annotations: it explains that the call creates a real appointment, that it fails rather than silently moving the user, and it enumerates failure reasons including taken, day_limit, locked, past, invalid, and error. It also discloses the required OAuth scope booking:write. These details are consistent with the non-readonly, non-idempotent annotations.

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?

The description is front-loaded with the core action and prerequisites, then covers return values and authorization. Every sentence carries useful information, and the failure reason list is compact rather than bloated.

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?

Because there is no output schema, the description appropriately explains the return contract: ok=true with booked date and time, or ok=false with a reason. It also covers authorization, slot provenance, and booking limits, which is complete for a mutation tool of this complexity.

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%, and the schema already documents date format, Europe/Kyiv timezone, slot-start format, and the get_availability prerequisite. The description reinforces that both parameters are required and repeats the format expectations, but adds little parameter-level meaning beyond the schema.

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?

The description states a specific verb and resource: "Creates a real appointment with the vertebrologist on the user's behalf." It distinguishes booking from merely checking availability by requiring that the slot come from get_availability, and the word "real" makes clear this is the actual booking action.

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

Usage Guidelines4/5

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

Usage context is clear: both date and time are required, and the slot must be one returned by get_availability. It also states the authorization prerequisite. It does not explicitly contrast book with siblings such as reschedule or cancel, so it falls short of full alternative routing.

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