Andrii Co. Notary & Apostille Assistant

reschedule_booking

Idempotent

Move one of the signed-in customer's own bookings to a new slot. Use when an authenticated customer wants a different time: find the order_id via my_bookings, take a fresh startUnix from search_availability (e.g. a morning slot), send it as scheduled_at. Returns a done confirmation; fails if the new time is not genuinely available, the booking is not yours, or not signed in.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`order_id`	Yes	The booking's order id (from my_bookings).
`scheduled_at`	Yes	The new slot's `startUnix` (from search_availability).

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`status`	No	Account tools: the booking's status after this call (Pending after book_appointment).
`message`	Yes	Customer-facing outcome; relay it as written — bookings are requests until the notary confirms.
`manageUrl`	No	Guest requests: the emailed confirm/cancel link, when one was minted (null otherwise).
`onAccount`	No	True when the request was filed on the signed-in customer's own account — they can then list it with my_bookings and change it with reschedule_booking / cancel_booking. Absent or false means a guest request, managed through the emailed link.
`reference`	No	Request / order reference for check_request_status (guest tools) or my_bookings (account tools).
`appendedToExisting`	No	True when existing_reference was given and the request was extended, not duplicated.
`ourComparableQuoteCents`	No	request_price_match only, when computable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "appendedToExisting": {
+      "description": "True when existing_reference was given and the request was extended, not duplicated.",
+      "type": "boolean"
+    },
+    "manageUrl": {
+      "description": "Guest requests: the emailed confirm/cancel link, when one was minted (null otherwise).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "description": "Customer-facing outcome; relay it as written — bookings are requests until the notary confirms.",
+      "type": "string"
+    },
+    "ok": {
+      "const": true,
+      "type": "boolean"
+    },
+    "onAccount": {
+      "description": "True when the request was filed on the signed-in customer's own account — they can then list it with my_bookings and change it with reschedule_booking / cancel_booking. Absent or false means a guest request, managed through the emailed link.",
+      "type": "boolean"
+    },
+    "ourComparableQuoteCents": {
+      "description": "request_price_match only, when computable.",
+      "type": "integer"
+    },
+    "reference": {
+      "description": "Request / order reference for check_request_status (guest tools) or my_bookings (account tools).",
+      "type": "string"
+    },
+    "status": {
+      "description": "Account tools: the booking's status after this call (Pending after book_appointment).",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "message"
+  ],
+  "type": "object"
+}

First observedJul 21, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already signal a non-read, non-destructive, idempotent operation. The description adds valuable behavior beyond that: it returns a done confirmation and fails under specific conditions (unavailable slot, not your booking, not signed in). It does not mention idempotency details, but the annotation covers that, so the bar is met and exceeded slightly.

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 a single dense sentence, but every clause earns its place: purpose, usage trigger, parameter sourcing, return signal, and failure modes. It is front-loaded with the core action and contains no filler.

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 an output schema present, the description does not need to explain return structure. It fully covers how to obtain both parameters, when to invoke, expected confirmation, and failure conditions. Nothing an agent needs to call this 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 baseline is 3. The description repeats the schema provenance (order_id from my_bookings, scheduled_at from search_availability) and adds a minor 'fresh' nuance, but it does not provide meaningful new semantics beyond what the schema already states.

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 opens with a specific verb+resource: 'Move one of the signed-in customer's own bookings to a new slot.' It clearly distinguishes from siblings like book_appointment (new booking) and cancel_booking, and the 'own bookings' phrase separates it from any admin-style rescheduling.

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?

It explicitly says 'Use when an authenticated customer wants a different time' and gives a concrete workflow: find order_id via my_bookings, get a fresh startUnix from search_availability, send it as scheduled_at. It also states failure conditions including incorrect ownership and missing authentication, which effectively tells the agent when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Andrii Co. Notary & Apostille Assistant tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?