biletall-mcp

biletall_flight_route

Compare flight fares between two Turkish cities for one route; get daily options with airline, airports, times, duration, and distance.

Instructions

Cheapest flights for one route. from_city / to_city: Turkish city names (e.g. "İstanbul" -> "Ankara") or slugs. limit 1..10. Returns the route summary (cheapest price in TRY, cheapest/most- active airline, flight count, duration, distance) plus the cheapest flights, each with its own date (ISO + Turkish), airline, origin/destination airports with IATA codes, departure/arrival times and price in TRY. Dates span the coming days — the page lists the cheapest per day.

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_city": "<from_city>",
      "to_city": "<to_city>"
    },
    "name": "biletall_flight_route"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`to_city`	Yes
`from_city`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description must carry the full behavioral burden, and it does a reasonable job: it discloses the currency (TRY), that results are per-day cheapest across upcoming days, the limit range, and the returned fields. It stops short of saying whether fares are live or cached, or anything about permissions or rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is front-loaded with the core purpose and parameter notes and has no filler. The long enumeration of return fields is somewhat redundant given an output schema exists, but it stays readable and does not bury the actionable information.

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?

For a three-parameter tool with an output schema, the description covers inputs, data semantics, and result shape adequately. The remaining gap is routing guidance against the bus/popular-routes/similar siblings, which would matter for a travel-search agent choosing among them.

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

Parameters5/5

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

Schema description coverage is 0%, and the description fully compensates: it states that both city parameters accept Turkish city names or slugs and gives a concrete example, and it pins the limit to the 1..10 range with an implied default of 10. Every parameter gains meaning beyond the bare schema titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific resource and outcome: cheapest flights for one route, with from_city/to_city inputs. It is clearly a flight-route lookup, which implicitly separates it from the bus-route and location-search siblings, but it never names an actual sibling to make the distinction explicit.

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?

Usage is only implied. The note that dates span the coming days and the page lists the cheapest per day tells an agent this is a browse-by-route tool rather than a specific-date search, but there is no statement of when to choose it over price stats, popular routes, or location search, and no preconditions are given.

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

Deploy Server