Dubai Table

Cancel booking

cancel_booking

DestructiveIdempotent

Cancel a request by reference and phone. There is no booking fee. The relationship manager confirms on WhatsApp.

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": {
      "ref": "<ref>",
      "phone": "<phone>"
    },
    "name": "cancel_booking"
  }
}

Input Schema

Name	Required	Description	Default
`ref`	Yes
`phone`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new context — no booking fee and WhatsApp confirmation by the relationship manager — which tells the agent about a follow-up channel, but it never states that the cancellation is final or what happens on failure/invalid reference.

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?

Three short sentences, action front-loaded, which is good. But 'There is no booking fee' is low-value for an agent's decision-making and the WhatsApp sentence mixes in operational detail without stating the outcome the agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 needn't be explained. Still, for a destructive, irreversible-feeling action with two undocumented required parameters, the description omits failure modes, whether cancellation can be undone, and how it relates to the checkout cancellation sibling.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden. 'By reference and phone' merely restates the two parameter names without giving format, provenance (where the reference comes from), or phone number conventions (country code, digits only).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Cancel') and the identifying inputs ('by reference and phone'), so the action is immediately understandable. However, it calls the target a 'request' rather than a 'booking', and never distinguishes this from the sibling 'cancel_checkout', which an agent could easily confuse it with.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus alternatives — most notably 'cancel_checkout', whose name strongly overlaps. There are no stated preconditions (e.g., must the booking exist, must it be pre-confirmation) and no exclusion cases.

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

All Dubai Table 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?