Cancun4me — Reservas de Hotel

cancel_booking

Cancela uma reserva. Se ainda estiver dentro do prazo gratis de uma tarifa reembolsavel, cancela e estorna automaticamente. Se estiver fora do prazo (ou for tarifa nao reembolsavel), a resposta vem com bloqueado: true — nesse caso avise o hospede que o cancelamento com multa precisa ser tratado manualmente (support@cancun4.me), NAO insista tentando de novo.

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": {
      "token": "<token>",
      "order_id": "<order_id>"
    },
    "name": "cancel_booking"
  }
}

Input Schema

Name	Required	Description	Default
`token`	Yes
`order_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 5, 2026

TDQS

A4.1/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key behavior: automatic cancellation plus refund inside the free window, and a `bloqueado: true` response field when the cancellation is refused. It does not address authentication/authorization around the token or whether a successful cancellation is reversible, which keeps it from a 5.

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

Conciseness4/5

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

Front-loaded with the core action, then the conditional branches. Efficient overall, though the manual-escalation instruction is stated at slightly greater length than strictly necessary.

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?

Behavioral and branch logic are well covered and the `bloqueado` response field is surfaced even without an output schema, but with no annotations and 0% schema coverage, the two required parameters remain entirely opaque to an agent.

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% and neither parameter is explained. The description never says what `token` is (auth credential vs. booking token) or what format `order_id` takes, so it fails to compensate for the schema gap on a tool where both params are required.

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 and resource ('Cancela uma reserva') and immediately qualifies the scope: auto-cancel/refund within the free window versus blocked outside it. No sibling tool performs cancellation, so no disambiguation is needed.

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 defines the success path (inside free period for a refundable rate), the failure path (outside period or non-refundable), and prescribes the exact follow-up: tell the guest it needs manual handling via support and do NOT retry. This is when/when-not guidance with an anti-pattern called out.

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

All Cancun4me — Reservas de Hotel 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?