wemake.holiday

Search flights

search_flights

Read-only

Live flight offers between two airports (IATA codes such as FRA, BKK). Round trip if return_date is given. Takes 10–25 seconds. Returns the cheapest offers with times, stops, baggage and a link.

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": {
      "from": "<from>",
      "to": "<to>",
      "depart_date": "<depart_date>"
    },
    "name": "search_flights"
  }
}

Input Schema

Name	Required	Description
`to`	Yes	arrival airport IATA code, e.g. BKK
`from`	Yes	departure airport IATA code, e.g. FRA
`adults`	No	number of adults (1-9), default 1
`language`	No	answer language, ISO code (default en)
`depart_date`	Yes	outbound date YYYY-MM-DD
`return_date`	No	optional return date YYYY-MM-DD (round trip)

Output Schema

Name	Required	Description	Default
`note`	No
`flights`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, non-idempotent, non-destructive, so safety is covered. The description adds genuinely useful operational context beyond that: "Takes 10-25 seconds" warns of latency, and it says results are the cheapest offers with times, stops, baggage and a link. No mention of rate limits or what happens when no offers exist.

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 short sentences, front-loaded with what the tool does, then the conditional behavior, then latency and return shape. No filler or repetition.

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 annotations and an output schema already present, the description covers the essentials: scope, IATA requirement, round-trip switch, latency, and a summary of returned fields. Minor gaps like currency/price basis and empty-result behavior are not addressed but the output schema likely covers structure.

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% and every parameter already has a description including the IATA examples and the round-trip meaning of return_date. The description only restates the return_date conditional in prose, adding no format, range, or constraint detail the schema lacks.

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?

Specific verb+resource: "Live flight offers between two airports (IATA codes such as FRA, BKK)", plus the round-trip conditional. An agent can tell immediately this is the flight-offer search and not a hotel, experience, or route-idea lookup.

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 gives context (live offers, 10-25s, cheapest offers returned) that implies when the tool fits, and the return_date sentence explains the round-trip switch. But it never states when to prefer or avoid it, no alternatives, no prerequisites or failure conditions.

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

All wemake.holiday 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?