Bota — car rental availability and bookings

Cancel a booking

cancel_booking

Destructive

Cancels a booking made through Bota. Without confirm it only returns the booking and whether it can be cancelled; with confirm=true it cancels it. Cancellation fees, if any, follow the company's terms.

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": {
      "company_id": "<company_id>",
      "booking_reference": "<booking_reference>",
      "email": "<email>"
    },
    "name": "cancel_booking"
  }
}

Input Schema

Name	Required	Description
`email`	Yes	Email the booking was made with. Required to prove the customer owns it.
`confirm`	No	true cancels the booking; omitted or false only previews it.
`language`	No	Language of the conversation, BCP-47 (es, en, pt-BR, fr, de, it…). Defaults to 'en'. Bota also answers in the language the customer writes.
`company_id`	Yes	Rental company id.
`booking_reference`	Yes	Booking reference from the customer's confirmation email.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 22, 2026

changedInput schema / properties / company_id / description

Previous value: -"Company id from list_rental_companies."New value: +"Rental company id."

changedInput schema / properties / confirm / description

Previous value: -"true only after the customer confirmed the cancellation of the booking shown by the previous call."New value: +"true cancels the booking; omitted or false only previews it."

AddedOct 21, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds the crucial mitigation that the tool is a dry-run by default and only mutates with confirm=true. It also notes cancellation fees are governed by company terms. It does not say whether cancellation is reversible or what happens to refunds, so not 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.

Conciseness5/5

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

Three short sentences, no waste, and the default-safe preview behavior is front-loaded right after the purpose statement. The fees note is short and earns its place by flagging a customer-facing consequence.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers the modes, the fee caveat, and the preview return value, which is enough for a 5-param tool with full schema coverage. It leaves minor gaps around what happens after a successful cancellation (refund timing, confirmation email), though with no output schema this is a modest shortfall.

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 description coverage is 100%, so the schema already documents every parameter including the `confirm` preview-vs-execute semantics and the email ownership proof. The description restates the confirm behavior rather than adding new meaning. Baseline 3 is appropriate.

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 and resource (cancel a booking) plus the scope ('made through Bota') and the two operating modes. It does not distinguish itself from the sibling confirm_booking, which is a real risk of confusion given the tool also has a `confirm` parameter.

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

Usage Guidelines4/5

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

Explicitly explains the two-mode usage: omit `confirm` to preview, pass `confirm=true` to actually cancel. That is clear operational guidance. It stops short of routing the agent between this tool and siblings like confirm_booking or get_booking_status.

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

All Bota — car rental availability and bookings 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?