Skip to main content
Glama
Sign In
Flyan

Flyan

by victorlane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

find_anywhere_under

Discover flights from your airport to anywhere under a given price. Enter departure airport, max price, and travel dates to find affordable destinations.

Instructions

Cheapest fares from from_airport to anywhere under max_price.

Useful for "where can I go for under £50 this weekend" style prompts.

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_airport": "<from_airport>",
      "max_price": "<max_price>",
      "from_date": "<from_date>",
      "to_date": "<to_date>"
    },
    "name": "find_anywhere_under"
  }
}

Input Schema

NameRequiredDescriptionDefault
from_airportYes
max_priceYes
from_dateYes
to_dateYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.3

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries full burden. It explains the core behavior (cheapest fares under a price) but does not specify return format, result count, or limitations (e.g., airline exclusions). It is adequate but not detailed.

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 short sentences: first defines the core function, second gives an illustrative use case. No filler or redundancy.

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?

For a tool with 4 required params and no schema descriptions, the description leaves out the date parameters. While an output schema exists, the description should explain all inputs. Adequate but incomplete.

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

Parameters2/5

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

Schema coverage is 0%; the description only indirectly explains 'from_airport' and 'max_price' while omitting 'from_date' and 'to_date' entirely. These are required, and their purpose is only hinted at by the example 'this weekend'. Missing explicit parameter definitions.

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?

The description clearly states it finds cheapest fares from a given airport to any destination under a max price, using a specific verb and resource. It distinguishes from siblings (e.g., 'find_flights' for specific flights) by emphasizing budget flexibility.

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?

The description provides a concrete example ('where can I go for under £50 this weekend') and implies the tool is for open-ended budget searches. However, it does not explicitly state when not to use or compare to siblings.

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

Deploy Server

Other Tools