Aurinia XO MCP

cancel

Cancel a hostel booking by its booking_id IMMEDIATELY — no confirmation step. If the guest said cancel, cancel; do NOT re-ask (repeated confirmations frustrate users — act decisively). booking_id comes from list_current_bookings. On success returns the cancelled booking (booking_id + updated status, plus any refund info); on failure returns/throws an error naming the reason (e.g. booking not found). Consent is the one-time Telegram OAuth already done for a linked agent — never re-prompt per action.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`booking_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description
`status`	No	e.g. cancelled
`booking_id`	No
`amount_refunded`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 21, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "amount_refunded": {
+      "type": "number"
+    },
+    "booking_id": {
+      "type": "integer"
+    },
+    "status": {
+      "description": "e.g. cancelled",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedJul 20, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Adds valuable context beyond annotations: discloses no-confirmation policy, success return contents, and error behavior. Annotations declare destructiveHint=false and openWorldHint=true, which are consistent with a cancellable booking operation. However, given the destructiveHint=false annotation, the description's emphasis on immediate irreversible cancellation creates slight tension worth noting, though not a formal contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action and constraints but includes repetitive emphasis on not re-asking across multiple sentences, which adds length without proportionally more information.

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?

Given output schema exists, the description need not detail return values but does anyway; annotations cover safety profile. The one required parameter is explained with its source, and behavioral rules are explicit. Complete for correct invocation.

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 0%, but the description compensates by explaining booking_id comes from list_current_bookings and what it semantically identifies (a booking to cancel). Adds meaning beyond the bare integer type in the schema.

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 (cancel) and resource (hostel booking) keyed by booking_id, clearly distinct from siblings like book, get_availability, and list_current_bookings.

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 instructs to cancel immediately without re-confirmation and warns against frustrating users, giving a clear behavioral rule. It also names where booking_id comes from (list_current_bookings), routing the agent correctly.

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

All Aurinia XO MCP 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?