SzuruSzuru – rezerwacja czyszczenia tapicerki

Anuluj rezerwację

cancel_booking

DestructiveIdempotent

PURPOSE: Cancels the verified customer's existing booking. Irreversible. WHEN TO USE: Only after the customer explicitly confirmed they want to cancel this specific booking (reference and date read back to them). WHEN NOT TO USE: Not to change the date (use reschedule_booking), never on an unclear request. REQUIRED: booking_reference, customer_grant (or a signed-in customer). reason and idempotency_key optional. SIDE EFFECTS: cancels the booking and notifies the customer by SMS/e-mail. Repeating the same call returns the same result.

Input Schema

TableJSON Schema

Name	Required	Description
`reason`	No	Optional short reason given by the customer
`session_id`	No	Optional. session_id from the previous result, if you have it. The server also recovers the session from quote_id / slot_id / confirmation_id / customer_grant.
`customer_grant`	No	customer_grant returned by verify_phone_code
`idempotency_key`	No	Optional. Same value when retrying the same request. If omitted, the server derives the key from the request, so a retry never creates a second booking.
`booking_reference`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`code`	No
`date`	No	YYYY-MM-DD, Polish time
`time`	No	HH:MM, Polish time
`error`	No	Stable machine-readable error id when success=false, e.g. missing_required_fields, unsupported_postcode, no_availability
`price`	No
`total`	No
`end_at`	No
`status`	No
`message`	No
`success`	Yes	true = operation done / data returned; false = see error
`currency`	No
`start_at`	No
`booking_id`	No	Booking reference to give the customer (same as booking_reference)
`can_cancel`	No
`session_id`	No
`can_reschedule`	No
`missing_fields`	No
`service_summary`	No
`booking_reference`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 1, 2026

addedInput schema / properties / customer_grant / description

Added value: +"customer_grant returned by verify_phone_code"

addedInput schema / properties / idempotency_key / description

Added value: +"Optional. Same value when retrying the same request. If omitted, the server derives the key from the request, so a retry never creates a second booking."

addedInput schema / properties / session_id / description

Added value: +"Optional. session_id from the previous result, if you have it. The server also recovers the session from quote_id / slot_id / confirmation_id / customer_grant."

changedInput schema / required

Previous value: -[
-  "booking_reference",
-  "idempotency_key"
-]New value: +[
+  "booking_reference"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "booking_id": {
+      "description": "Booking reference to give the customer (same as booking_reference)",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "booking_reference": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "can_cancel": {
+      "type": "boolean"
+    },
+    "can_reschedule": {
+      "type": "boolean"
+    },
+    "code": {
+      "type": "string"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "date": {
+      "description": "YYYY-MM-DD, Polish time",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "end_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Stable machine-readable error id when success=false, e.g. missing_required_fields, unsupported_postcode, no_availability",
+      "type": "string"
+    },
+    "message": {
+      "type": "string"
+    },
+    "missing_fields": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "price": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "service_summary": {
+      "type": "string"
+    },
+    "session_id": {
+      "type": "string"
+    },
+    "start_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "type": "string"
+    },
+    "success": {
+      "description": "true = operation done / data returned; false = see error",
+      "type": "boolean"
+    },
+    "time": {
+      "description": "HH:MM, Polish time",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "total": {
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "success"
+  ],
+  "type": "object"
+}

First observedSep 20, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations cover the safety profile (destructiveHint, idempotentHint, readOnlyHint=false), and the description adds substance beyond them: notification side effects via SMS/e-mail, the irreversibility of the operation, and the repeated-call behavior. The auth requirement (customer_grant or signed-in customer) is also disclosed.

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?

Labeled sections (PURPOSE / WHEN TO USE / WHEN NOT TO USE / REQUIRED / SIDE EFFECTS) front-load the decision-critical information, and each line carries a distinct fact with 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?

An output schema exists so return values need not be described, and the description still covers everything an agent needs: preconditions, auth path, irreversible consequences, notification side effects, and idempotent retry behavior.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 80%, so the baseline is 3, but the description adds real meaning: it distinguishes which fields are required vs optional and clarifies that customer_grant can be replaced by a signed-in customer. session_id is omitted from the description but is well documented in the schema itself.

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 the specific verb and resource ("Cancels the verified customer's existing booking") and immediately flags the irreversible nature. It is clearly distinguishable from reschedule_booking, which is explicitly named as the wrong tool for date changes.

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 an explicit WHEN TO USE precondition (customer explicitly confirmed the specific booking, reference and date read back) and an explicit WHEN NOT TO USE with the named alternative (reschedule_booking) plus a prohibition on unclear requests. Nothing is left to inference.

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

All SzuruSzuru – rezerwacja czyszczenia tapicerki 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?