Skip to main content
Glama

Bandago Van Rentals

by com.bandago
OverviewDiscussionsAdmin

check_availability

Check which vehicles are available for rental on specific dates and locations. Uses the scheduling engine to account for existing reservations, vehicle positioning, and fleet consolidation. Returns a list of available vehicle types (rate codes) with availability urgency labels.

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 (four-digit year, e.g. 2026-12-18)
rate_codeNoOptional vehicle type filter: an exact rate_code from list_rate_codes (e.g. 'Transit Std', 'SP15'), a display name ('Transit Medium Roof'), or a brand word ('Sprinter', 'Transit') to include every type of that brand. Omit to check all types.
start_cityYes2-letter pickup location code (e.g., 'LA', 'NA', 'SF')
start_dateYesRental start date, YYYY-MM-DD (four-digit year, e.g. 2026-12-18)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / rate_code / description
      Previous value: -"Filter by vehicle type/rate code (e.g., 'Ford Transit', 'Sprinter'). Omit to check all types."New value: +"Optional vehicle type filter: an exact rate_code from list_rate_codes (e.g. 'Transit Std', 'SP15'), a display name ('Transit Medium Roof'), or a brand word ('Sprinter', 'Transit') to include every type of that brand. Omit to check all types."
  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. 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, the description carries the behavioral burden. It discloses that availability is computed by a scheduling engine that accounts for reservations, vehicle positioning, and fleet consolidation, and it states the return shape (rate codes with urgency labels). A minor gap is that the urgency labels are not defined.

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 concise sentences with no filler: the purpose is front-loaded, followed by algorithmic context and return behavior. Every sentence contributes 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?

For a 5-parameter tool with no output schema or annotations, the description covers purpose, computation context, and return content. It doesn't detail the meaning or range of urgency labels, but an agent has enough to select and call the tool correctly.

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 each parameter already has a description. The tool description adds context around dates/locations but does not need to repeat parameter details; baseline 3 applies.

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?

Description names a specific verb ('Check'), a resource ('vehicles available for rental'), and the key filtering dimensions (specific dates and locations). The return statement about available vehicle types/rate codes distinguishes it from siblings like get_rate_quote and list_rate_codes.

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 description establishes a clear use case: checking availability for rental on given dates and locations. It does not explicitly name sibling alternatives or exclusions (e.g., when to use get_rate_quote instead), so it falls short of full routing guidance.

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