Skip to main content
Glama

biletall_price_stats

Retrieve today's bus fare statistics for a Turkish route: journey and company counts, min/median/mean/max ticket prices in TRY, and cheapest price per company.

Instructions

Price statistics for a bus route (today): journey count, min / median / mean / max ticket price in TRY across the 30 cheapest journeys the site lists, company count, and the cheapest price per company. from_city / to_city: Turkish city names or slugs.

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_price_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
to_cityYes
from_cityYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does meaningful work: it discloses that the statistics are computed over only 'the 30 cheapest journeys the site lists', which implies max is not the true route maximum, and that all prices are in TRY. It does not cover permissions, failure behaviour, or what happens when a route has no departures, so it stops short of full disclosure.

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?

Two sentences, front-loaded with the tool's purpose and scope, then the parameter note. The metric list is dense but each item is informative. Minor redundancy in re-listing output fields when an output schema exists.

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 two-parameter read-only statistics tool with an output schema, the description supplies the essentials an agent needs: what is measured, over what sample, in what currency, and for what day. The re-enumeration of return fields is slightly redundant given the output schema, and empty-result behaviour is unstated.

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 description coverage is 0%, so the description must compensate and largely does: it states that from_city and to_city accept 'Turkish city names or slugs', which the bare string schema does not. It does not say whether names must be exact matches or how ambiguity (e.g. multiple cities sharing a prefix) is resolved.

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 description opens with a specific verb-plus-resource, 'Price statistics for a bus route', and enumerates the metrics returned (journey count, min/median/mean/max price, company count, cheapest per company). That is far more concrete than the bare tool name and distinguishes it from route-search siblings in substance, though it never names an alternative tool to contrast against.

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: '(today)' and 'the 30 cheapest journeys the site lists' tell the agent the scope is same-day fare comparison, but there is no explicit 'use this when…' or 'do not use for…' guidance. An agent can infer the intent, but nothing routes it away from biletall_bus_route for schedule lookups.

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