Skip to main content
Glama

biletall_popular_routes

Retrieve popular bus routes on biletall.com with TRY fares, from/to slugs, and route URLs, limited to 1–30 results.

Instructions

Most-travelled bus routes on biletall.com with prices: route name, from/to slugs, cheapest price in TRY and the route URL. limit 1..30. Source: the homepage / /otobus-seferleri most-travelled list.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "biletall_popular_routes"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It does disclose useful traits: the results are a curated popularity list from a specific page, prices are in TRY, and a route URL is included. It says nothing about caching/freshness, rate limits, or whether the list is static, which would matter for an unannotated read tool.

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?

Roughly three short lines, front-loaded with the resource and immediately followed by the returned fields and the parameter bound. The 'Source:' fragment is slightly telegraphic but still earns its place by explaining provenance.

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?

An output schema exists, so return values need not be spelled out, yet the description still summarizes them harmlessly. For a single-optional-parameter read tool this is close to complete; only the absence of freshness/caching context keeps it from a 5.

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?

Schema coverage is 0% and the only parameter, 'limit', has no minimum/maximum in the schema (just a default of 15). The description supplies the missing constraint 'limit 1..30', which is genuine meaning beyond the structured field and prevents out-of-range calls.

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?

States a specific verb+resource: most-travelled bus routes on biletall.com, plus the exact fields returned (route name, from/to slugs, cheapest TRY price, route URL). The word 'bus' implicitly separates it from biletall_flight_route, but no sibling is named explicitly, so it stops short of a 5.

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?

The 'Source: the homepage / /otobus-seferleri most-travelled list' line tells the agent where the data comes from, which implies this is a discovery tool for popular routes. However, there is no explicit 'use this when' statement and no guidance about when to prefer biletall_bus_route or biletall_price_stats instead.

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