Skip to main content
Glama

Full of Joy · Croatia private tours

Check dates and price

check_availability
Read-onlyIdempotent

Check which dates are open for a tour and the indicative price for a group size. Give one date, or a range (date_from and date_to, at most 62 days).

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": {
      "tour": "<tour>"
    },
    "name": "check_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOne date, YYYY-MM-DD.
tourYesTour key from list_tours.
optionNoOption key from get_tour. Default: the first option (private driver).
date_toNoEnd of a range, YYYY-MM-DD.
personsNoNumber of travellers. Default 2.
date_fromNoStart of a range, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/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 closed-world, so the safety profile is covered. The description adds genuine context beyond them: the 62-day ceiling on ranges and the fact that the price is only 'indicative' for a group size, warning the agent not to treat it as a quote.

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, both load-bearing. The primary capability is front-loaded and the calling constraint follows immediately, with no filler.

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 read-only, closed-world availability query with full schema coverage and no output schema, the description covers what is queried and roughly what comes back (open dates plus indicative price). It does not say how unavailability is represented, a minor gap given the absence of an output schema.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds two constraints the schema does not encode: date vs. date_from/date_to are alternative modes rather than combinable, and the range span is bounded at 62 days. That is real semantic value beyond the field-level descriptions.

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: checking open dates and indicative price for a tour at a given group size. It is clearly distinct from get_tour/list_tours (catalog reads) and request_booking (a commitment), though it never names those siblings to reinforce the contrast.

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?

It tells the agent how to frame the query (one date, or a range capped at 62 days), which is practical guidance, but gives no explicit when-to-use/when-not guidance relative to request_booking. The 'check before booking' role is implied rather than stated.

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