Bandago Van Rentals

email_quote

Email a saved rate quote to a customer. Stores the quote under a token and includes a resume link in the email — when the customer clicks it, they're dropped into the booking flow with their vehicle, dates, and insurance selections already filled in. Rate-limited to 3 emails per day per address.

Input Schema

TableJSON Schema

Name	Required	Description
`email_to`	Yes	Customer email address to send the quote to.
`end_city`	No	2-letter return location code. Defaults to start_city.
`end_date`	Yes	Rental end date (YYYY-MM-DD)
`end_time`	No	Return time, 24hr format without colon. Default '1000'.
`rate_code`	Yes	Vehicle type/rate code (e.g., 'Ford Transit', 'Sprinter')
`start_city`	Yes	2-letter pickup location code
`start_date`	Yes	Rental start date (YYYY-MM-DD)
`start_time`	No	Pickup time, 24hr format without colon (e.g., '1000'). Default '1000'.
`include_cdw`	No	Pre-select Damage Waiver (CDW) on the resumed booking page. Default false — shown as optional add-on.
`include_pai`	No	Pre-select Personal Accident Insurance (PAI). Default false.
`include_rlp`	No	Pre-select Primary Liability (RLP). Default false.
`include_sli`	No	Pre-select Supplemental Liability (SLI). Default false.
`discount_code`	No	Promotional or discount code
`include_cdw_plus`	No	Quote Damage Waiver Plus, the upgrade that lowers the customer's damage responsibility from the standard deductible to the Plus deductible for a per-day upcharge. Only honored when include_cdw is also true and Plus is currently offered; otherwise the quote falls back to the standard waiver. Call explain_coverage for the current deductibles and price. Default false.

TDQS

A4.2/5.0

Behavior4/5

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

The description discloses notable behaviors not visible from schema alone: the token storage, the resume link that pre-fills selections, and the rate limit of 3 emails per day per address. Since there are no annotations, this adds valuable context about side effects and constraints.

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 three concise sentences, front-loaded with the main action. It packs the purpose, key behavior, and a constraint with no 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 provides a good high-level context for a complex 14-parameter tool with no output schema. It explains the emailing flow and rate limit. However, it does not mention the return value or what happens on rate-limit failure, leaving a minor gap given the lack of annotations and output schema.

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?

The schema covers all 14 parameters with descriptions (100% coverage), so the baseline is 3. The tool description mentions that insurance selections are pre-filled, which relates to the boolean parameters, but it does not add specific parameter-level details beyond what the schema already provides.

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 clearly states the tool's purpose with a specific verb and resource: 'Email a saved rate quote to a customer.' It distinguishes itself from sibling tools like get_rate_quote or get_reservation_link by focusing on the email-sending action and the resume-link behavior.

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 implies the usage context: it sends a saved quote and describes the resume flow, which helps an agent understand when to use it. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of a 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 tools Inspect

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

Need Help?