Skip to main content
Glama

Aurinia — book across venues via your AI assistant

reschedule

Idempotent

Moves an existing booking at a network venue. Takes provider_id and item; for a doctor that is {date, from, to}, and the move is atomic within the same day — if the target slot is taken in the race, the user keeps the slot they already held, so either outcome leaves them with a booking. A move to a different day is a fresh booking, so book is the right call for that. Support varies by venue: a hostel has no reschedule, where a cancel followed by a new book is the equivalent. If the user is not yet authorized at that venue the call returns a consent link instead. Authorization: one Telegram consent per venue, 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": {
      "provider_id": "<provider_id>",
      "item": "<item>"
    },
    "name": "reschedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYesWhat to move, interpreted by the venue. Doctor: {date:'YYYY-MM-DD', from:'HH:MM' (slot held now), to:'HH:MM' (new slot, same day)}. A hostel has no reschedule — cancel and book again there.
provider_idYesVenue id as returned by find_providers (e.g. rudko-vertebrolog).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / item / description
      Added value: +"What to move, interpreted by the venue. Doctor: {date:'YYYY-MM-DD', from:'HH:MM' (slot held now), to:'HH:MM' (new slot, same day)}. A hostel has no reschedule — cancel and book again there."
    • addedInput schema / properties / provider_id / description
      Added value: +"Venue id as returned by find_providers (e.g. rudko-vertebrolog)."
  2. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=false and idempotentHint=true, and the description meaningfully reinforces that safety profile with the same-day atomicity guarantee and the 'user keeps the slot they already held' failure outcome. It also discloses a non-obvious return mode: an authorization consent link is returned instead of a move when the user isn't authorized at that venue, and one Telegram consent per venue persists for later calls. That is solid added context, though it stops short of describing the success response shape or how the consent flow is completed.

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 core action and the atomicity guarantee, then proceeds to alternatives, venue support, and authorization in a logical order. It is somewhat long and the doctor {date, from, to} breakdown duplicates the input schema almost word for word, which is the main wasted sentence.

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 two-parameter nested mutation with no output schema, the description covers the essential unknowns: atomicity, race-failure behavior, cross-day alternatives, per-venue capability differences, and the authorization/consent requirement. Nothing an agent needs in order to call it correctly or explain the outcome appears to be 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 both parameters are already documented, including the nested {date, from, to} structure and the meaning of from versus to. The description largely restates the doctor item shape verbatim rather than adding new syntax or format guidance, so the baseline 3 is appropriate even though the failure semantics around from/to are useful.

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 an existing booking') plus the scope ('at a network venue'), and then explicitly contrasts itself with the siblings book and cancel. An agent can distinguish reschedule from a fresh booking without reading another 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-not-to-use rules with named alternatives: a move to a different day should use book, and a venue without reschedule support (hostel) should use cancel followed by a new book. Both the exclusion condition and the replacement tool are 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