Bota — car rental availability and bookings

Search available cars and prices

search_availability

Read-only

Search available vehicles with real prices for a company, office and dates. Prices are identical to the company's own web chat (mandatory charges, one-way and time rules included). Returns numbered offers and the session_id of this booking session.

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>",
      "pickup_office": "<pickup_office>",
      "pickup_date": "<pickup_date>",
      "return_date": "<return_date>",
      "driver_age": "<driver_age>"
    },
    "name": "search_availability"
  }
}

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.
`driver_age`	Yes	Main driver's age. The price and the available cars depend on it.
`promo_code`	No
`session_id`	No	Booking session id returned by a previous call for this company (offers, selection, customer details). Omitted, a new session starts.
`pickup_date`	Yes	YYYY-MM-DD, office-local.
`pickup_time`	No	HH:MM, office-local. Default 10:00.
`return_date`	Yes	YYYY-MM-DD, office-local.
`return_time`	No	HH:MM, office-local. Default 10:00.
`pickup_office`	Yes	Pickup office name or id.
`return_office`	No	Return office name or id when different (one-way).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 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 / driver_age / description

Previous value: -"Main driver's age. Ask the customer before searching: the price and the available cars depend on it."New value: +"Main driver's age. The price and the available cars depend on it."

changedInput schema / properties / pickup_office / description

Previous value: -"Pickup office name (from list_offices) or id."New value: +"Pickup office name or 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."

Changed2 schema fields changedOct 21, 2026

addedInput schema / properties / driver_age / description

Added value: +"Main driver's age. Ask the customer before searching: the price and the available cars depend on it."

changedInput schema / required

Previous value: -[
-  "company_id",
-  "pickup_office",
-  "pickup_date",
-  "return_date"
-]New value: +[
+  "company_id",
+  "pickup_office",
+  "pickup_date",
+  "return_date",
+  "driver_age"
+]

First observedSep 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the lower bar applies; the description still earns credit by disclosing that prices match the company's own web chat and include mandatory charges, one-way and time rules, and that it returns numbered offers plus a session_id — meaningful behavior beyond structured fields.

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, front-loaded with the core action and scope, then pricing fidelity, then return shape. No filler; each sentence carries distinct information.

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?

With no output schema, the description compensates by stating the return shape (numbered offers, session_id) and pricing guarantees. Combined with a 91%-documented 11-parameter schema this is largely complete, missing only explicit guidance on prerequisite lookups.

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 coverage is 91%, so the schema already documents nearly every parameter including date formats, defaults and the driver_age price dependency. The description adds little parameter-specific detail beyond mentioning session_id, so the 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 ('Search') plus resource ('available vehicles with real prices') and the scoping dimensions (company, office, dates). It is clearly the availability-search step in the booking flow, though it never names a sibling tool to differentiate itself explicitly.

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

Usage Guidelines3/5

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

Usage is implied by the booking-flow framing and the note that passing session_id continues an existing session, but there is no explicit 'use this when…' or steering to alternatives like list_rental_companies or list_offices for resolving a company/office first.

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?