biletall-mcp

biletall_bus_route

Find the cheapest bus journeys between two Turkish cities for today, comparing prices, companies, stations, and departure times to plan a low-cost trip.

Instructions

Cheapest bus journeys for one route, today. from_city / to_city: Turkish city names (e.g. "İstanbul" -> "Ankara") or slugs. limit 1..30. Returns the route summary (cheapest price in TRY, journey count, cheapest/most-active company, duration, route rating) plus the cheapest journeys (company, bus type, origin city + station, destination city + station, price in TRY, departure/arrival times). The page lists today's departures.

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_bus_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

A3.5/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: results are always today's departures with no date control, and the response pairs a route summary with the cheapest journeys. It does not state that the operation is read-only, nor anything about authentication, rate limits, or result caching.

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 core purpose and scope are front-loaded in the first sentence, and the parameter notes follow immediately. The long parenthetical enumerating return fields is the weakest part, padding the text with detail an output schema should already carry.

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?

Since an output schema exists, the description needn't enumerate return fields, but otherwise it covers purpose, parameter formats, result bounds, and the critical caveat that data is limited to today. The main gap is the absence of any statement about side effects or permissions for a tool with zero annotations.

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 0%, so the description must compensate, and it does explain all three parameters meanings: from_city/to_city accept Turkish city names or slugs (with an example), and limit is bounded to 1..30. However it omits the documented default of 10 and gives no guidance on how are results ordered when limit truncates them.

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?

"Cheapest bus journeys for one route, today" gives a specific resource (bus journeys) and a ranking criterion (cheapest) scoped to a single origin-destination pair. The bus framing implicitly separates it from biletall_flight_route without naming it, so an agent can distinguish the two, but no sibling is explicitly referenced.

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 implied rather than stated: an agent can infer this is for a single city-pair bus query, but the description never says when to prefer it over biletall_popular_routes or biletall_price_stats, nor does it set any exclusions. The "today" scope is the only routing signal given.

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

Deploy Server