ATA Travel

search_network_availability

Read-onlyIdempotent

Find accommodations across the ATA Travel Network with real-time pricing. Use when dates are known. Supports filtering by amenities, views, property type, and free-text keyword to handle vague requests.

Input Schema

Name	Required	Description
`views`	No	Filter by room views. e.g. ['Ocean', 'Mountain', 'Garden', 'City']
`adults`	No	Number of adults
`budget`	No	Optional additional budget constraint. Clarify missing currency or basis before calling. Do not combine with legacy maxPrice/maxPriceCurrency.
`checkIn`	Yes	Check-in date (YYYY-MM-DD)
`keyword`	No	Text matched against property name/description. Use for a required text match; use preferences for optional style preferences.
`checkOut`	Yes	Check-out date (YYYY-MM-DD)
`children`	No	Number of children
`location`	No	Optional city, state, or country. Omit when the traveler knows dates but is open to ATA's current destinations.
`maxPrice`	No	Maximum total price filter
`amenities`	No	Filter by amenities on property or rooms. e.g. ['Pool', 'Gym', 'Pet Friendly', 'Spa']
`preferences`	No	Open-ended soft ranking signals. These do not exclude otherwise valid stays.
`propertyType`	No	e.g. 'Hotel', 'Apartment', 'Villa'
`priceAudience`	No
`displayCurrency`	No	Optional 3-letter currency for approximate traveler-facing display conversion. Native property currency remains authoritative.
`internalAgentKey`	No
`maxPriceCurrency`	No	Currency for maxPrice when filtering across mixed property currencies. If omitted, maxPrice is compared to each property's native currency.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 23, 2026

changedInput schema / properties / keyword / description

Previous value: -"Free-text keyword matched against property name/description. Great for vibe searches like 'boutique', 'beachside', 'romantic'."New value: +"Text matched against property name/description. Use for a required text match; use preferences for optional style preferences."

Changed1 schema field changedOct 16, 2026

addedInput schema / properties / budget

Added value: +{
+  "additionalProperties": false,
+  "description": "Optional additional budget constraint. Clarify missing currency or basis before calling. Do not combine with legacy maxPrice/maxPriceCurrency.",
+  "properties": {
+    "amount": {
+      "description": "Maximum amount in the explicitly supplied currency and basis.",
+      "exclusiveMinimum": 0,
+      "type": "number"
+    },
+    "basis": {
+      "description": "Required explicit basis. Per-night means a stay-average allowance, not a ceiling on each night. Per-person means every adult and child equally; clarify other interpretations.",
+      "enum": [
+        "TOTAL_STAY",
+        "PER_NIGHT",
+        "PER_PERSON_STAY",
+        "PER_PERSON_PER_NIGHT"
+      ],
+      "type": "string"
+    },
+    "currency": {
+      "description": "Required 3-letter budget currency. Never infer from location or displayCurrency.",
+      "pattern": "^[A-Za-z]{3}$",
+      "type": "string"
+    },
+    "scope": {
+      "default": "PRICED_STAY",
+      "description": "PRICED_STAY compares the accommodation total including configured taxes/fees. ALL_IN requires complete mandatory charges; currently ATA cannot verify completeness and will return labeled alternatives only.",
+      "enum": [
+        "PRICED_STAY",
+        "ALL_IN"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "amount",
+    "currency",
+    "basis"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedJul 15, 2026

changedInput schema / properties / location / description

Previous value: -"City, State, or Country (e.g. 'Puerto Vallarta', 'Mexico', 'California')"New value: +"Optional city, state, or country. Omit when the traveler knows dates but is open to ATA's current destinations."

addedInput schema / properties / preferences

Added value: +{
+  "description": "Open-ended soft ranking signals. These do not exclude otherwise valid stays.",
+  "items": {
+    "maxLength": 120,
+    "minLength": 1,
+    "type": "string"
+  },
+  "maxItems": 6,
+  "type": "array"
+}

changedInput schema / required

Previous value: -[
-  "location",
-  "checkIn",
-  "checkOut"
-]New value: +[
+  "checkIn",
+  "checkOut"
+]

First observedJun 29, 2026

TDQS

A3.6/5.0

Behavior3/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 only that pricing is real-time, which signals live/volatile data but says nothing about rate limits, result caps, pagination, or response shape. Useful but thin beyond what annotations provide.

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 short sentences with zero padding, and the core purpose leads before the usage condition. Could be marginally tighter, but every clause carries information an agent can act on.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 16 parameters, a nested budget object and no output schema, the schema covers most of the parameter semantics well, but the description says nothing about result shape, result limits, or how to interpret ranked output. It also does not explain the relationship between the modern budget object and legacy maxPrice, leaving that entirely to the schema. Adequate but with clear gaps for a tool of this complexity.

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 carries the heavy lifting, including the nested budget object and the maxPrice/maxPriceCurrency legacy interaction. The description's mention of amenities, views, property type and keyword filtering merely restates filterable dimensions the schema documents in detail. Baseline 3 is appropriate.

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 ('Find accommodations') plus scope ('across the ATA Travel Network with real-time pricing'). It implicitly separates itself from the flexible-dates sibling via 'Use when dates are known', but never names search_flexible_network_availability or search_property_availability, so differentiation is inferential rather than explicit.

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

Usage Guidelines4/5

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

'Use when dates are known' gives a clear triggering condition and effectively rules out the flexible-search sibling without naming it. The note that free-text keyword 'handles vague requests' tells the agent how to proceed when the request is fuzzy. No explicit exclusions or named alternatives, which keeps it short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ATA Travel tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?