Skip to main content
Glama
Sign In

Bota — car rental availability and bookings

by com.bota-chat
OverviewDiscussionsAdmin

Select extras

select_extras

Adds optional extras (child seat, additional driver, coverage…) to the booking in progress by extra id; an empty list continues without extras. Only for companies with booking_via_agents=true.

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>",
      "extras": "<extras>"
    },
    "name": "select_extras"
  }
}

Input Schema

NameRequiredDescriptionDefault
extrasYesExtra ids to add; empty array = no extras.
languageNoLanguage 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_idYesRental company id.
session_idYesBooking session id returned by a previous call for this company (offers, selection, customer details). Omitted, a new session starts.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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."
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description contributes real context beyond that: the empty-array continuation semantics and the company eligibility constraint. It does not say whether repeated calls replace or append to previously selected extras, nor how invalid extra ids are handled.

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?

A single dense sentence with the action front-loaded, the skip path and eligibility constraint trailing. No filler and nothing repeated from structured fields.

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?

For a 4-parameter booking mutation with no output schema, the definition covers purpose, the continuation case, and the eligibility gate. Error behavior and whether extras replace prior selections are the only meaningful gaps.

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 100%, so every parameter including the extras array and empty-array convention is already documented in the schema. The description's mention of 'by extra id' matches rather than extends the schema, so baseline 3 applies.

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: adds optional extras (child seat, additional driver, coverage) to the booking in progress by extra id, with concrete examples of what an 'extra' is. It fits a clear booking-flow step among siblings like select_offer and confirm_booking, though it doesn't name which sibling precedes or follows it.

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?

Provides a concrete eligibility gate: 'Only for companies with booking_via_agents=true', which tells the agent when this tool is valid. It also clarifies the skip path (empty list continues without extras), but does not explicitly route to or exclude any sibling tool.

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 toolsInspect
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