Skip to main content
Glama

Bandago Van Rentals

by com.bandago
OverviewDiscussionsAdmin

get_reservation_link

Generate a link to start a reservation on Bandago's website with dates and locations pre-filled. The customer will choose their vehicle and complete the booking on the website. This is the only valid way to produce a booking URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
end_cityNo2-letter return location code. Defaults to start_city if not specified (round-trip).
end_dateYesRental end date (YYYY-MM-DD). A one-day rental returns the next day; 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 start_time. Valid values: 0900, 0930, 1000, 1030, 1100, 1130, 1200, 1230, 1300, 1330, 1400, 1430, 1500, 1530, 1600, 1630.
rate_codeNoPre-select one vehicle type: the exact rate_code from list_rate_codes or from the get_rate_quote result (e.g. 'Transit Std', 'SP15'). Use the same value you quoted so the page matches the quote. Omit to let the customer choose.
start_cityYes2-letter pickup location code (e.g., 'LA', 'NA', 'SF')
start_dateYesRental start date (YYYY-MM-DD)
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.

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)"New value: +"Rental end date (YYYY-MM-DD). A one-day rental returns the next day; never equal to start_date."
    • changedInput schema / properties / rate_code / description
      Previous value: -"Filter to a specific vehicle type (e.g., 'Ford Transit', 'Sprinter'). When provided, only this vehicle will be shown on the booking page."New value: +"Pre-select one vehicle type: the exact rate_code from list_rate_codes or from the get_rate_quote result (e.g. 'Transit Std', 'SP15'). Use the same value you quoted so the page matches the quote. Omit to let the customer choose."
  2. Changed1 schema field changed
    • addedInput schema / properties / rate_code
      Added value: +{
+  "description": "Filter to a specific vehicle type (e.g., 'Ford Transit', 'Sprinter'). When provided, only this vehicle will be shown on the booking page.",
+  "type": "string"
+}
  3. Added

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description carries the burden of explaining behavior. It usefully clarifies that the customer, not the agent, chooses the vehicle and completes the booking on the website, and that this is the only valid way to produce a booking URL. It does not describe return format, permissions, or other side-effect details, but for a link-generation tool the stated context is reasonably adequate.

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?

The description is two sentences with no wasted words. It front-loads the core purpose, then adds the critical clarification that the customer completes the booking, and finishes with a strong selection rule. Every sentence earns its place.

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 tool has rich schema documentation for all 7 parameters, and the description provides the main behavioral context: it generates a pre-filled reservation link, the customer finishes booking on the website, and this is the only valid way to produce such a URL. Since there is no output schema, a slightly more explicit statement of the return value format would make it fully complete, but the word 'link' and the stated purpose largely cover this.

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 the parameters are already well documented. The description adds no new parameter-level meaning beyond saying that dates and locations will be pre-filled, which is a minor behavioral note rather than an enrichment of individual parameter semantics. A baseline of 3 is appropriate.

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 states a specific action ('Generate a link'), a specific resource ('a reservation on Bandago's website'), and the key behavior of pre-filling dates and locations. It also differentiates itself by noting this is the only valid way to produce a booking URL, which clearly separates it from the sibling tools.

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 phrase 'This is the only valid way to produce a booking URL' gives a clear selection rule for when to use this tool. However, it does not explicitly name alternatives or state when NOT to use this tool in favor of siblings like check_availability or list_rate_codes, so it stops just short of a full 5.

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