reschedule
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
| Name | Required | Description | Default |
|---|---|---|---|
| item | Yes | 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. | |
| provider_id | Yes | Venue id as returned by find_providers (e.g. rudko-vertebrolog). |