Flyan

explore_destinations

Retrieve all Ryanair destinations reachable from an origin airport, grouped by country. Quickly answer which countries and cities are accessible from a specific departure point.

Instructions

Every destination Ryanair flies to from origin, grouped by country.

Returns {country_code: [{iata, name, city, region}]}. No fare lookup, just the network. Good for answering "what countries can I reach from X" or "does origin fly to destination at all".

Input Schema

TableJSON Schema

Name	Required	Description	Default
`origin`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.3Jun 19, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Discloses no fare lookup, purely network exploration; with no annotations, this adequately conveys behavior for a read-only query.

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?

Two concise sentences front-loading purpose and including return format example; no wasted words.

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?

Output schema exists and description explains return structure; single parameter, no additional context needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Single parameter 'origin' is clearly implied as the starting airport via backticks; schema coverage is 0% but description adds meaning to the parameter.

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?

Clear verb 'explore' and specific resource 'destinations from origin'; distinguishes from sibling tools by stating 'no fare lookup, just the network'.

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?

Explicit examples of when to use: answering reachable countries or if a destination is served. No explicit when-not-to-use, but sibling context implies alternatives for pricing.

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

Deploy Server