Skip to main content
Glama

Bandago Van Rentals

by com.bandago

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.

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)
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/rate code (e.g., 'Ford Transit', 'Sprinter')
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

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It partially discloses internal logic ('Bandago rate engine with DIA multipliers and multi-jurisdiction tax calculations') but does not explicitly state it is a read-only operation, whether the quote depends on availability, or what happens with invalid inputs. No side effects or prerequisites are addressed.

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?

Two sentences: the first front-loads the purpose and output specifics, the second adds rate-engine context. Every word earns its place, with no filler or redundancy.

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?

The description lists expected output components (day rate, insurance, mileage, taxes, total), partially compensating for the lack of an output schema. It also gives useful rate-engine context. However, it omits guidance on prerequisites (e.g., availability check, location code meanings) and error handling, so it is not fully complete.

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 the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides; it only lists output components and high-level rate-engine behavior.

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?

The description opens with a specific verb and resource: 'Get a full pricing breakdown for a rental' and enumerates the breakdown components (day rate, insurance, mileage, taxes, grand total). This clearly distinguishes it from sibling tools like check_availability (availability) and email_quote (sending quotes).

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

Usage Guidelines2/5

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

The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention that check_availability might be a prerequisite or that email_quote could send the generated quote. Usage context is only implied by the tool's purpose.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0
Disambiguation5/5

Each tool targets a distinct action: availability, quoting, coverage, reservation lookup, link generation, locations, and vehicle types. There is no meaningful overlap that could cause an agent to select the wrong tool.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using lowercase snake_case (check_, email_, explain_, get_, list_). The convention is uniform across the set.

Tool Count5/5

Eight tools is well-scoped for a rental information and assistance server. Each tool serves a clear purpose and the count is within the ideal range for a domain-specific MCP.

Completeness2/5

The set has significant gaps: email_quote references a 'saved rate quote' but there is no save_quote tool to create one, and get_my_reservation mentions an admin lookup tool that isn't present. This creates dead ends and will cause agent failures in follow-through workflows.

Resources