Bota — car rental availability and bookings

Confirm the booking

confirm_booking

Destructive

Confirms the summarised booking with its confirmation_token, which proves the customer saw that exact summary. Creates the reservation in the company's reservation system and returns the confirmation code (and a payment link when the company requires prepayment). An on-request booking comes back pending the company's confirmation and without a code yet.

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>",
      "session_id": "<session_id>",
      "confirmation_token": "<confirmation_token>"
    },
    "name": "confirm_booking"
  }
}

Input Schema

Name	Required	Description
`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.
`session_id`	Yes	Booking session id returned by a previous call for this company (offers, selection, customer details). Omitted, a new session starts.
`confirmation_token`	Yes	confirmation_token from the response that showed the booking summary.

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 / session_id / description

Previous value: -"Session id returned by a previous call for this company. Omit on the first call; ALWAYS pass it back on the next ones so Bota keeps the conversation (offers, selection, customer details)."New value: +"Booking session id returned by a previous call for this company (offers, selection, customer details). Omitted, a new session starts."

First observedSep 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this as a write with destructiveHint=true and idempotentHint=false; the description adds the crucial side effect (reservation is created in the company's external reservation system) and the return shape (confirmation code, plus payment link when prepayment is required). It still doesn't say the action is irreversible or that retries are unsafe, which is the main gap given idempotentHint=false.

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 tight sentences, front-loaded with the core action and its precondition, then side effects, then the edge case. No filler.

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?

There is no output schema, so the description carries the return-value burden and does so well, covering the confirmation code, the conditional payment link, and the pending on-request case. It is thin on failure/retry behaviour for a non-idempotent destructive write, which is what keeps it short of a 5.

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 all four parameters are already documented in the schema. The description reinforces the meaning of confirmation_token (proof the summary was seen) but adds no syntax, format, or constraints for company_id, session_id, or language beyond what the schema states.

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 ('Confirms the summarised booking') and immediately ties it to the mechanism (confirmation_token proving the customer saw that summary). It also distinguishes this terminal step from the earlier offer/selection steps, so an agent can place it in the booking flow without opening siblings.

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?

The precondition for calling it is explicit: the booking must already be summarised and the customer must have seen that exact summary, evidenced by a confirmation_token. There is no explicit when-not guidance or routing to cancel_booking / get_booking_status, which keeps it from a 5.

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?