Skip to main content
Glama

check_availability

Read-onlyIdempotent

Check real-time availability for a service on specific dates.

Dates should be ISO format (YYYY-MM-DD). Returns availability status and pricing.
Call get_services first to obtain the service_id. Follow with get_price_quote
for dual-currency pricing before offering to book.

``price_total_amount_minor`` is the total for the whole party, not a unit
price. Quote that figure to the traveller and pass it back as
``quoted_total_minor`` on create_booking. ``price_breakdown.summary`` says
who is being charged what ("2 adults + 1 child"); state it, so a party of
adults is never booked silently on a service with a child fare.

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": "check_availability"
  }
}

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'.
time_slotNoOptional time slot in HH:MM format, e.g. '15:00'. For scheduled services like Lava Show, checks a specific show time. Omit to see all available slots for the date.
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.
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 readOnly/idempotent/non-destructive, and the description goes well beyond them: it explains that price_total_amount_minor is a whole-party total rather than a unit price, that the figure must be echoed as quoted_total_minor on create_booking, and that price_breakdown.summary must be stated to avoid booking adults on a child fare. This is exactly the kind of downstream-consumption context annotations cannot carry.

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 action and the workflow sequence, then the price/party cautions. Every sentence is functional, though the second paragraph is dense and the backticked field names make it slightly heavier than necessary for the information conveyed.

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 an 8-parameter read tool with a full output schema and rich annotations, nothing an agent needs is missing: workflow prerequisites, date format, the party-total pricing interpretation, and the hand-off to create_booking are all present.

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% and the per-parameter descriptions (including the detailed guest_count/adults_count/children_count rules) already do the heavy lifting. The description's date-format note repeats the schema, and its party-composition caution is framed around the returned price_breakdown rather than adding new parameter syntax. Baseline 3 is appropriate.

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 ('Check real-time availability for a service on specific dates') plus what it returns (availability status and pricing). It also differentiates itself from siblings by naming get_services, get_price_quote, and create_booking in the workflow, so an agent can place it precisely.

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 an explicit sequencing protocol: obtain service_id from get_services first, then call this tool, then get_price_quote for dual-currency pricing before offering to book. That is both a when-to-use condition and the correct ordering relative to alternatives.

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