agentweb-mcp

search_flights

Search flights across booking.com and kiwi.com and automatically compare prices to return the cheapest option. Includes airlines, times, stops, and booking links.

Instructions

Search flights across multiple sources (booking.com + kiwi.com) and return the cheapest. Compares prices automatically — one call gets the best deal. Returns airlines, prices, times, stops, duration, source, and booking links. Results in ~3 seconds.

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": "<depart>"
    },
    "name": "search_flights"
  }
}

Input Schema

Name	Required	Description	Default
`from`	Yes	Origin airport IATA code (e.g. 'CPH', 'JFK', 'LHR')
`to`	Yes	Destination airport IATA code (e.g. 'FCO', 'CDG', 'NRT')
`depart`	Yes	Departure date in YYYY-MM-DD format
`return`	No	Return date in YYYY-MM-DD format (omit for one-way)
`adults`	No	Number of adult passengers (default: 2)
`cabin`	No	Cabin class (default: ECONOMY)	ECONOMY
`sort`	No	Sort results by price, speed, or direct flights only	cheapest
`limit`	No	Maximum results to return (default: 10)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.17.0Jun 21, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations, so description carries full burden. Discloses approximate response time (~3 seconds) and return fields, but omits authentication requirements, rate limits, or cost implications.

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 sentences, no filler. Front-loaded with key purpose and behavior, every sentence adds value.

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?

No output schema, but description lists return fields explicitly. Missing details on error handling or pagination, but adequate for a standard flight search tool.

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 100%, so schema already documents each parameter thoroughly. Description adds marginal value by implying aggregation, but not needed beyond schema.

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?

Explicitly states verb 'search' and resource 'flights', specifies it searches across multiple sources and returns cheapest, distinguishing it from siblings like kiwi_search_flights.

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?

Clear context: compares prices across sources for best deal. No explicit when-not or alternative names, but the multi-source aggregation is a strong indication of use case.

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