aviasales-mcp

Overview Schema Source Related Servers Discussions Admin

get_latest_prices

Read-onlyIdempotent

Retrieve recently found flight fares from other travellers' searches for a route or the whole cache. Use it to spot new price drops, then book through the provided agency link.

Instructions

Get the most recently found flight prices from other travellers' searches.

Use when the user wants the latest fares that just appeared, on one route or across the whole cache. For a specific trip on chosen dates use search_flights instead. Prices are per adult (cached); passenger parameters are encoded into each booking_link.

These rows come from the older v2 shape: they name the selling agency rather than an airline, carry no flight number, and their booking_link is reconstructed from the route and dates.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Max results (1-100, default 20).
`adults`	No	Number of adult passengers, 1-9 (default 1).
`market`	No	2-letter market whose price cache to read. Defaults to the server's configured market.
`origin`	No	Origin IATA code. Optional.
`infants`	No	Number of infants under 2, 0-8 (default 0). Cannot exceed the number of adults; the excess is trimmed.
`one_way`	No	One-way tickets only.
`children`	No	Number of children 2-11 years, 0-8 (default 0). Adults plus children cannot exceed 9; the excess is trimmed.
`currency`	No	Price currency (3 letters). Defaults to the server's currency.
`trip_class`	No	"economy", "comfort", "business" or "first" (default "economy").	economy
`destination`	No	Destination IATA code. Optional.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.3Oct 15, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations cover the read-only, idempotent safety profile, so the bar is lower, but the description adds real behavioral context: rows are cached v2-shape data naming an agency rather than an airline, lack flight numbers, and have reconstructed booking_links. The only thing not addressed is pagination/ordering of results, which is minor given the output schema exists.

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?

Three tight paragraphs: purpose and scope first, the routing alternative second, the data-shape caveat last. Every sentence adds information an agent needs; nothing is redundant.

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 a 10-parameter read tool with full schema coverage, full annotations, and an output schema, the description fills the remaining gaps: routing to the correct sibling and warning about the legacy v2 row shape. Nothing material is missing.

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%, so every parameter is already documented in the schema, and the output schema covers the response. The description adds only incidental parameter-relevant notes (per-adult pricing, passenger details encoded in booking_link), not syntax or format guidance beyond the schema. 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?

Names a specific verb (get) and resource (latest flight prices from other travellers' searches), and explicitly contrasts itself with search_flights. An agent can disambiguate it from all twelve siblings without opening a schema.

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 trigger ('when the user wants the latest fares that just appeared') plus a named alternative ('For a specific trip on chosen dates use search_flights instead'). Both the use and the when-not-to-use case are stated.

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

Deploy Server