Skip to main content
Glama

Bandago Van Rentals

by com.bandago
OverviewDiscussionsAdmin

get_rate_quote

Get a full pricing breakdown for a rental including day rate, insurance options, mileage allowance, applicable taxes, and grand total. Uses the Bandago rate engine with DIA (days-in-advance) multipliers and multi-jurisdiction tax calculations. grand_total includes every optional coverage; subtotal plus sales_tax is the price without optional coverage.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoCustomer email (used for VIP rate detection)
end_cityNo2-letter return location code. Defaults to start_city.
end_dateYesRental end date, YYYY-MM-DD (four-digit year, e.g. 2026-12-18). A one-day rental returns the next day at the same time; never equal to start_date.
end_timeNoReturn time in 24hr format without colon (e.g., '1000' for 10:00 AM, '1400' for 2:00 PM). Defaults to '1000'. Valid values: 0900, 0930, 1000, 1030, 1100, 1130, 1200, 1230, 1300, 1330, 1400, 1430, 1500, 1530, 1600, 1630.
rate_codeYesVehicle type as an exact rate_code from list_rate_codes, e.g. 'Transit Std' (Ford Transit medium roof, 15 passengers), 'SP15' (Sprinter 15-passenger), 'SP Crew 12'. A display name such as 'Transit Medium Roof' is also accepted. Brand-only values such as 'Ford Transit' or 'Sprinter' match several types and are rejected with the candidates listed.
start_cityYes2-letter pickup location code
start_dateYesRental start date, YYYY-MM-DD (four-digit year, e.g. 2026-12-18)
start_timeNoPickup time in 24hr format without colon (e.g., '1000' for 10:00 AM, '1400' for 2:00 PM). Defaults to '1000'. Valid values: 0900, 0930, 1000, 1030, 1100, 1130, 1200, 1230, 1300, 1330, 1400, 1430, 1500, 1530, 1600, 1630.
discount_codeNoPromotional or discount code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / end_date / description
      Previous value: -"Rental end date, YYYY-MM-DD (four-digit year, e.g. 2026-12-18)"New value: +"Rental end date, YYYY-MM-DD (four-digit year, e.g. 2026-12-18). A one-day rental returns the next day at the same time; never equal to start_date."
    • changedInput schema / properties / rate_code / description
      Previous value: -"Vehicle type/rate code (e.g., 'Ford Transit', 'Sprinter')"New value: +"Vehicle type as an exact rate_code from list_rate_codes, e.g. 'Transit Std' (Ford Transit medium roof, 15 passengers), 'SP15' (Sprinter 15-passenger), 'SP Crew 12'. A display name such as 'Transit Medium Roof' is also accepted. Brand-only values such as 'Ford Transit' or 'Sprinter' match several types and are rejected with the candidates listed."
  2. Changed4 schema fields changed
    • changedInput schema / properties / end_date / description
      Previous value: -"Rental end date (YYYY-MM-DD)"New value: +"Rental end date, YYYY-MM-DD (four-digit year, e.g. 2026-12-18)"
    • addedInput schema / properties / end_date / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
    • changedInput schema / properties / start_date / description
      Previous value: -"Rental start date (YYYY-MM-DD)"New value: +"Rental start date, YYYY-MM-DD (four-digit year, e.g. 2026-12-18)"
    • addedInput schema / properties / start_date / pattern
      Added value: +"^\\d{4}-\\d{2}-\\d{2}$"
  3. Changed2 schema fields changed
    • addedInput schema / properties / end_time
      Added value: +{
+  "description": "Return time in 24hr format without colon (e.g., '1000' for 10:00 AM, '1400' for 2:00 PM). Defaults to '1000'. Valid values: 0900, 0930, 1000, 1030, 1100, 1130, 1200, 1230, 1300, 1330, 1400, 1430, 1500, 1530, 1600, 1630.",
+  "type": "string"
+}
    • addedInput schema / properties / start_time
      Added value: +{
+  "description": "Pickup time in 24hr format without colon (e.g., '1000' for 10:00 AM, '1400' for 2:00 PM). Defaults to '1000'. Valid values: 0900, 0930, 1000, 1030, 1100, 1130, 1200, 1230, 1300, 1330, 1400, 1430, 1500, 1530, 1600, 1630.",
+  "type": "string"
+}
  4. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool uses DIA multipliers, multi-jurisdiction taxes, and clarifies that grand_total includes all optional coverage while subtotal plus sales_tax does not. It also discloses rate_code acceptance rules (display names accepted, brand-only values rejected). This is substantial, though it could mention rate limits or auth if applicable.

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 sentences, front-loaded with the core purpose, followed by two concise behavioral clarifications. No wasted words; every sentence earns its place. The structure is efficient and scannable.

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 9-parameter tool with no output schema, the description covers the main output semantics (grand_total vs. subtotal) and the key behavioral nuance of rate_code. It does not enumerate all possible return fields, but that is not expected without an output schema. The description is complete enough for an agent to call it correctly and interpret the primary results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful value beyond the schema by explaining the rate_code acceptance behavior (display names accepted, brand-only values rejected) and the relationship between grand_total, subtotal, and sales_tax, which are not in the schema. It also implies the DIA multiplier effect on pricing, though it doesn't detail every parameter.

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 ('Get a full pricing breakdown for a rental') and enumerates the exact components returned (day rate, insurance, mileage, taxes, grand total). This clearly distinguishes it from siblings like check_availability or list_rate_codes without needing to open them.

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?

The description explains what the tool does and mentions the rate engine and tax logic, but it does not explicitly state when to use this tool versus alternatives. There is no 'use this when you need pricing' or 'for availability use check_availability instead' guidance, so the usage context is implied rather than explicit.

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

All Bandago Van Rentals 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