Skip to main content
Glama

get_price_quote

Read-onlyIdempotent

Get a dual-currency price quote for a service.

Returns pricing in ISK and the tourist's likely currency based on language_code.
Provider-backed lodging quotes include quote_basis (for example ``1 bed``)
and unit_kind; name that sellable unit when presenting the quote.
Call after check_availability confirms dates are open. Use the quote to inform
the user before calling create_booking.
If the quote lists traveller_questions, ask the traveller these before
create_booking and send each answer in special_requests as its line says.

``total_amount_minor`` is the total for the whole party. Pass it back as
``quoted_total_minor`` on create_booking: if the price has moved since you
quoted it, the booking is refused rather than charged at a figure the
traveller never agreed to.

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": {
      "operator_id": "<operator_id>",
      "service_id": "<service_id>",
      "check_in": "<check_in>",
      "check_out": "<check_out>"
    },
    "name": "get_price_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
check_inYesArrival date in ISO format (YYYY-MM-DD), e.g. '2026-06-15'.
check_outYesDeparture date in ISO format (YYYY-MM-DD), e.g. '2026-06-18'.
service_idYesService identifier for a specific room type, tour, or activity. Obtain from get_services using the operator_id.
guest_countNoThe TOTAL number of travellers, including any children. For two adults and one child pass guest_count=3, adults_count=2, children_count=1, NOT guest_count=2. Getting this wrong books too few seats and the operator's manifest is short a person on the day.
operator_idYesUnique operator slug, e.g. 'fosshotel-reykjavik' or 'arctic-adventures'. Obtain from search_operators. Do not guess — always look up first.
adults_countNoHow many of guest_count are adults. Optional, but always pass it: when given, adults_count + children_count must equal guest_count, and the call is refused if it does not, rather than booking the wrong party.
language_codeNoISO language code for currency conversion, e.g. 'en', 'de', 'fr'.en
children_countNoHow many of guest_count are children. Pass this whenever any traveller is a child and the service lists a child price.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, so the safety profile is covered; the description adds non-obvious behavior beyond that — a stale price causes the booking to be refused rather than charged, and traveller_questions must be resolved before booking. It also explains how the returned unit should be presented to the traveller, which no annotation conveys.

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-loaded with the core purpose, then proceeds in workflow order (dates open -> quote -> questions -> booking), with no filler sentences. It is somewhat long and mixes return-field formatting guidance into prose, but each paragraph carries actionable information for the agent.

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?

For a read-only quote tool with a rich schema and an output schema, the description covers everything an agent needs: prerequisites, party-total semantics, unit presentation, traveller question handling, and the downstream handoff of quoted_total_minor. Nothing material is left to inference for correct invocation or use of the result.

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 all eight parameters (including the guest_count/adults_count/children_count consistency rule) are already documented in the schema, making 3 the baseline. The description adds a little meaning by tying language_code to the second currency and clarifying that total_amount_minor covers the whole party, but it does not add syntax or constraints beyond the schema's own text.

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?

Opens with a specific verb and resource: 'Get a dual-currency price quote for a service', then narrows the output shape (ISK plus the tourist's likely currency derived from language_code). It is clearly distinguishable from siblings like check_availability and create_booking, and even names the provider-specific sellable unit concept (quote_basis, unit_kind).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit ordering: call after check_availability confirms dates are open, use the quote to inform the user before calling create_booking. It also states what to do with traveller_questions (ask before booking, send answers in special_requests) and what to do with the returned total (pass back as quoted_total_minor). Both the when and the when-next are covered.

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