Skip to main content
Glama

search_flexible_network_availability

Read-onlyIdempotent

Search participating ATA properties for availability and prices across a flexible date window. Defaults to a window 28–56 days from today, three nights, and two adults only when those values are missing; always return those defaults as explicit assumptions. Preferences are soft ranking signals, not a closed taxonomy.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_flexible_network_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewsNoOptional soft view preferences for flexible discovery.
adultsNoAdult guests. Defaults to 2.
nightsNoLength of stay. Defaults to 3 nights.
childrenNoChild guests. Defaults to 0.
locationNoOptional city, state, country, neighborhood, or building. Omit when the traveler is open to ATA's current destinations.
maxPriceNoMaximum total stay price.
amenitiesNoOptional soft amenity preferences for flexible discovery.
maxResultsNoMaximum priced stays to return. Defaults to 4.
preferencesNoOpen-ended soft preferences inferred from the traveler's own words or live network facets.
propertyTypeNoOptional soft property-type preference; it ranks results and is reported as a difference when unavailable.
latestCheckInNoLatest acceptable check-in date. Defaults to 56 days from today.
priceAudienceNo
displayCurrencyNoOptional traveler-facing display currency.
earliestCheckInNoEarliest acceptable check-in date. Defaults to 28 days from today.
internalAgentKeyNo
maxPriceCurrencyNoCurrency for maxPrice when filtering mixed native currencies.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety profile is covered. The description adds genuinely useful traits annotations cannot express: silent defaulting of dates, nights and adults, and the requirement to surface those defaults as explicit assumptions. It also discloses that ranking signals are soft rather than a closed taxonomy — behavior an agent could easily get wrong.

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?

Three sentences, all front-loaded with the core action first and qualifications after. Minor friction: 'always return those defaults as explicit assumptions' is phrased as an instruction to the caller rather than as a description of tool behavior, but the density is appropriate for a 16-parameter tool.

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 16-parameter, zero-required, no-output-schema tool, the description covers the highest-risk ambiguities: default injection, soft vs. hard filtering, and search scope. It does not mention the maxResults cap of 6 or how mixed-currency pricing and priceAudience behave, but those are documented in the schema and are secondary to correct invocation.

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 88%, so the schema already documents nearly all 16 parameters, including the 28/56-day defaults and the defaults for nights and adults. The description mostly restates those defaults rather than adding syntax or interpretation; its only real addition is explaining that views, amenities, propertyType and preferences are soft ranking inputs, which the schema already hints at.

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?

States a specific verb and resource: 'Search participating ATA properties for availability and prices across a flexible date window.' The word 'flexible' implicitly separates it from fixed-date siblings like search_network_availability and search_property_availability, but no sibling is named explicitly, so the distinction is inferred rather than stated.

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 only implied: the traveler supplies a window rather than exact dates, and preferences are soft signals. There is no explicit 'use this when…' guidance and no reference to the alternative availability-search tools, leaving the agent to infer when this is preferred over search_network_availability or search_property_availability.

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