Skip to main content
Glama

Rudko — vertebrologist (Chernivtsi, Ukraine)

reschedule

Moves the user's appointment to another free slot on the same day, atomically. Takes date (YYYY-MM-DD), from (HH:MM, the slot held now) and to (HH:MM, the new slot). Returns ok=true with moved_to, or ok=false with a reason: taken (the target slot was taken in the race — the user keeps the slot they already held, so either outcome leaves them with an appointment — that is the point of the atomic move), not_found, invalid, error. A move to a different day is a fresh booking and needs no atomic hold, so book is the right call for that. 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": {
      "date": "<date>",
      "from": "<from>",
      "to": "<to>"
    },
    "name": "reschedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesFree slot to move to, HH:MM, same day, as returned by get_availability.
dateYesDay of the appointment, YYYY-MM-DD. The move stays within this day.
fromYesSlot the user holds now, HH:MM.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / date / description
      Added value: +"Day of the appointment, YYYY-MM-DD. The move stays within this day."
    • addedInput schema / properties / from / description
      Added value: +"Slot the user holds now, HH:MM."
    • addedInput schema / properties / to / description
      Added value: +"Free slot to move to, HH:MM, same day, as returned by get_availability."
  2. Added

TDQS

A4.2/5.0
Behavior3/5

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

Annotations declare it is not read-only, not idempotent, open-world, and not destructive, so the safety profile is already partly covered. The description still adds real value beyond them: atomicity, the race outcome where the user retains their original slot, the enumerated failure reasons, and the required OAuth scope booking:write. That is solid added context, though the destructiveHint=false framing could have been reconciled more explicitly with the fact that the user's existing slot is released.

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?

The purpose and scope lead the sentence, followed by parameters, returns, and routing. It is information-dense but slightly overpacked into a single paragraph, and the parenthetical explaining why the user keeps their slot in the 'taken' case is wordy though genuinely useful.

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?

With no output schema, the description fully specifies the return contract (ok=true with moved_to, ok=false with enumerated reasons) and the authorization prerequisite. Combined with the routing rule to book, an agent has everything needed to call it correctly and interpret the result.

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 describes all three fields including format hints (YYYY-MM-DD, HH:MM) and the same-day constraint. The description restates the same semantics rather than adding new ones, so 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 and resource ('Moves the user's appointment to another free slot') plus a hard scope constraint ('on the same day, atomically'). It also implicitly separates itself from a plain booking by framing the operation as a move from an existing held slot.

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?

Explicitly routes the agent: same-day move uses this tool, while 'A move to a different day is a fresh booking and needs no atomic hold, so book is the right call for that.' It also points at get_availability as the source of valid target slots via the schema.

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