Skip to main content
Glama

Quote a rental for a date and ZIP

build_quote
Read-only

Build a complete, real quote for one rental on a specific date and delivery zip: exact dated item price, availability, delivery fee, that date's minimum order, the total, and the booking link. Use this the moment you know the product, the date and the zip - it is the fastest way to answer 'how much?' properly. If you are missing the date or zip, ask the customer for it (never guess a zip from their IP or city) and then call this.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "product_name": "<product_name>",
      "event_date": "<event_date>",
      "zip": "<zip>"
    },
    "name": "build_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit delivery zip the customer gave you
itemsNoTwo or more items for the SAME party: pass them all here (product_name = the first one) to get ONE order total with one delivery fee. Never add up separate quotes.
couponNoOptional: CHAT10 once you have offered it, or a code the customer typed. Returns with_coupon, the exact discounted total, so you never do discount math yourself.
end_dateNoONLY for a multi-day rental (keep it over the weekend, Friday to Sunday, overnight to another day): the PICKUP day, YYYY-MM-DD. event_date is then the DROP-OFF day. Returns one price for the whole span.
end_timeNoWhen the party ends, in their words ("1pm"). For an attended rental, when it should stop running - not the pickup time.
quantityNoHow many of this item, default 1
event_dateYesEvent date YYYY-MM-DD
start_timeNoWhen the party starts, in their words ("10am", "2:30pm"). For a rental with an attendant (mechanical bull etc.), when it should start running. Pass start_time AND end_time whenever they have said them: the price depends on party length.
product_nameYesProduct name or close description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / end_date
      Added value: +{
      +  "description": "ONLY for a multi-day rental (keep it over the weekend, Friday to Sunday, overnight to another day): the PICKUP day, YYYY-MM-DD. event_date is then the DROP-OFF day. Returns one price for the whole span.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description's job is to add behavioral context, which it does: the quote is authoritative with one delivery fee per order, and a coupon returns the exact discounted total so the agent must not do discount math. It also discloses the return contents, though it could say more about what happens when an item is unavailable on the date.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose and outputs before the usage rules, and every sentence carries actionable content. It is slightly padded with conversational phrasing ('the fastest way to answer how much properly') and parenthetical asides, but nothing is genuinely redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 9 parameters, no output schema, and annotations covering safety, the description fills the remaining gaps by describing what a successful quote returns and how to handle multi-item orders, coupons, and missing inputs. An agent has everything needed to call it correctly and interpret the result.

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 earns above that by adding real meaning beyond the schema: party length drives the price, so start_time and end_time should both be passed when known, and a zip must come from the customer rather than inference. It reinforces rather than restates the parameter intent.

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 (build a quote for one rental) plus the exact inputs (date, delivery zip) and enumerates the outputs: dated item price, availability, delivery fee, minimum order, total, and booking link. This clearly separates it from siblings like delivery_fee and product_info, which cover single facets rather than a full quote.

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?

Gives an explicit trigger ('the moment you know the product, the date and the zip') and a precondition with a when-not rule: if the date or zip is missing, ask the customer and never infer a zip from IP or city. It does not name a specific alternative tool for partial information, but the entry criteria are otherwise unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources