Skip to main content
Glama

Price quote

get_quote
Read-onlyIdempotent

An itemised price for one accommodation, stay and party, including chosen extras and any discount or voucher code. Use it to show the guest the exact total and the amount payable now before starting the booking.

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": {
      "campsite": "<campsite>",
      "accommodation_id": "<accommodation_id>",
      "check_in": "<check_in>",
      "check_out": "<check_out>",
      "adults": "<adults>"
    },
    "name": "get_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
dogsNoNumber of dogs.
adultsYesNumber of adults.
extrasNoOptional extras from get_campsite (electric hook-up, firewood, late checkout...).
infantsNoNumber of infants, only at campsites whose age_policy has infants_under_age. Infants are never charged.
campsiteYesThe campsite slug, as returned by search_campsites.
check_inYesArrival date, YYYY-MM-DD.
childrenNoNumber of children. Which ages count as a child varies by campsite: see age_policy on get_campsite (default: everyone under 18).
check_outYesDeparture date, YYYY-MM-DD. Must be after check_in.
voucher_codeNoA gift voucher code, if the campsite sells them.
discount_codeNoA promotional code the guest has, if the campsite accepts them.
club_membershipNoOptional. The same club, status and number as start_booking takes; include it so a joining fee shows in the quoted total.
accommodation_idYesaccommodation_id from check_availability or get_campsite.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / club_membership
      Added value: +{
      +  "description": "Optional. The same club, status and number as start_booking takes; include it so a joining fee shows in the quoted total.",
      +  "properties": {
      +    "club": {
      +      "description": "The club key from club_memberships on get_campsite.",
      +      "type": "string"
      +    },
      +    "number": {
      +      "description": "Membership number, or membership email for clubs whose identifier is email.",
      +      "maxLength": 255,
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "\"member\" if the guest already belongs to the club, \"join\" to join at booking where the club allows it.",
      +      "enum": [
      +        "member",
      +        "join"
      +      ],
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / extras / items / properties / extra_id / description
      Added value: +"The extra's id from get_campsite."
    • addedInput schema / properties / extras / items / properties / quantity / description
      Added value: +"How many of this extra. Default 1."
  2. Changed2 schema fields changed
    • changedInput schema / properties / children / description
      Previous value: -"Number of children (under 18)."New value: +"Number of children. Which ages count as a child varies by campsite: see age_policy on get_campsite (default: everyone under 18)."
    • addedInput schema / properties / infants
      Added value: +{
      +  "default": 0,
      +  "description": "Number of infants, only at campsites whose age_policy has infants_under_age. Infants are never charged.",
      +  "maximum": 20,
      +  "minimum": 0,
      +  "type": "integer"
      +}
  3. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already carry the read-only, idempotent, non-destructive safety profile, so the description only needs to add what they don't cover. It adds that the result is itemised and splits a total from an 'amount payable now', but says nothing about quote validity/expiry, whether prices are guaranteed, or whether extras availability is re-checked — all meaningful for a pricing tool.

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?

Two sentences, zero filler: the first defines the output, the second defines the use. Both are front-loaded with the information an agent needs to decide whether to call it.

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 12-parameter read-only tool with nested objects and full schema coverage, the description covers purpose, sequencing and the shape of the return (itemised total plus payable now) despite there being no output schema. It is not fully complete — quote lifetime and the fact that a quote does not reserve anything are absent — but nothing essential to calling it correctly is missing.

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 every parameter is documented in the schema itself, including the club_membership joining-fee note and the per-campsite age_policy for children. The description only gestures at extras, discount_code and voucher_code collectively and adds no syntax or constraint detail beyond the schema; the baseline of 3 applies.

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 names a specific verb and resource — an itemised price for one accommodation, stay and party, with extras and discount/voucher applied. It is clearly distinguishable from mutation siblings via the phrase 'before starting the booking', though it does not explicitly distinguish itself from check_availability, which also takes dates and party size.

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?

'Use it to show the guest the exact total and the amount payable now before starting the booking' gives a concrete usage moment and sequence relative to start_booking. It stops short of an explicit exclusion (e.g. don't call before check_availability confirms the stay) or of stating that the quote holds no inventory.

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