Skip to main content
Glama

Check availability

check_availability
Read-onlyIdempotent

Live availability at one campsite for a stay and party. Returns the accommodation types that can take the party with the total price and the amount due at checkout, and explains why the others cannot (fully booked, minimum stay, adults only, no dogs).

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>",
      "check_in": "<check_in>",
      "check_out": "<check_out>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
dogsNoNumber of dogs.
adultsNoNumber of adults.
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds real value on top: it is a live lookup (not cached) and it returns rejection reasons for unavailable accommodation (fully booked, minimum stay, adults only, no dogs), which tells the agent what it can learn from a negative result.

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?

One tight sentence that front-loads the scope ('live availability at one campsite') and then the return contract. No filler, no restated title, no redundancy.

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?

With no output schema, the description correctly takes on the job of explaining the return payload: eligible accommodation types, total price, amount due at checkout, and the reasons others fail. It stops short of describing the response shape (flat list vs. object, whether pricing is per-night or total stay) but is otherwise sufficient for a read-only lookup.

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 already documented, including unit limits and the infants/children age-policy caveats. The description only frames them collectively as 'stay and party' and adds no syntax or constraint detail beyond the schema, so the baseline 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 ('live availability at one campsite') and scopes it to a stay and party, which is far more than a restatement of the name. It does not explicitly contrast itself with siblings like get_quote or start_booking, so the boundary between 'check availability' and 'get a quote' is left implicit.

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

Usage Guidelines3/5

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

Usage is implied by 'live availability for a stay and party' – an agent can infer this is a pre-booking feasibility check – but there is no explicit when-to-use, when-not, or pointer to alternatives such as get_quote for pricing or start_booking to commit.

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