Skip to main content
Glama

Preview a Fiji vehicle-rental quote

preview_rental_quote
Read-only

Calculate a non-binding, non-persisted rental quote. Availability and payment remain with the representative rental company.

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": {
      "vehicle_slug": "<vehicle_slug>",
      "pickup_at": "<pickup_at>",
      "return_at": "<return_at>",
      "driver_age": "<driver_age>"
    },
    "name": "preview_rental_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketNoFJ
pickup_atYes
return_atYes
driver_ageYes
agent_sourceNo
vehicle_slugYes
quote_currencyNoFJD
pickup_locationNoNadi International Airport
return_locationNoNadi International Airport
agent_session_idNo

Output Schema

NameRequiredDescriptionDefault
marketYes
statusYes
previewYes
persistedYes
next_actionYes
continue_urlYesSame-site booking form for customer review.
booking_eligible_from_previewYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedOutput schema / properties / continue_url
      Added value: +{
      +  "description": "Same-site booking form for customer review.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "market",
      -  "status",
      -  "preview",
      -  "persisted",
      -  "booking_eligible_from_preview",
      -  "next_action"
      -]New value: +[
      +  "market",
      +  "status",
      +  "preview",
      +  "persisted",
      +  "booking_eligible_from_preview",
      +  "continue_url",
      +  "next_action"
      +]
  2. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description usefully adds that the result is non-binding and non-persisted and that availability and payment are handled by the rental company — real value beyond the annotations. It does not address failure modes, date validation, or currency handling, so this is solid but not rich.

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?

Two sentences, front-loaded with the core action and the key non-persistence guarantee, with no filler. It is efficiently written, though the terseness comes at the cost of coverage captured under other dimensions.

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

Completeness2/5

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

An output schema exists, so return values need not be explained, but a 10-parameter pricing tool with zero schema descriptions is under-specified by two sentences. Nothing tells the agent how the market/currency defaults interact, what driver_age 21-85 implies, or what happens when pickup and return locations differ.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has 0% description coverage across 10 parameters, so the description must carry the burden of explaining them, and it mentions none. There is no explanation of market, quote_currency, pickup_location, driver_age bounds, or the agent_source/agent_session_id attribution fields. The agent is left to guess from field names alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Calculate a non-binding, non-persisted rental quote.' Combined with the title's 'Fiji vehicle-rental' scoping, an agent can distinguish this from the transfer and private-driver quote siblings. It stops short of naming those siblings explicitly, so it lands at 4 rather than 5.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternatives, even though preview_transfer_quote and preview_private_driver_quote are near-identical in shape. The phrase 'non-binding' implies a pre-booking preview, but the agent must infer that this is the rental path rather than a transfer or driver path.

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