Skip to main content
Glama

obilet_search_bus_journeys

Search bus journeys for a route and date, compare departure times, durations, and TRY prices, and sort results by price, departure, or duration.

Instructions

Bus journeys for one route + date. origin_id / destination_id: bus location ids from obilet_search_locations (e.g. İstanbul Avrupa 349 -> Ankara 356). date: YYYY-MM-DD (e.g. "2026-11-07"). sort: "price_asc" (cheapest first, default), "departure" (earliest first), "duration" (shortest first). limit 1..24. Returns journey id, partner, bus type, seats, origin/destination stations, departure/arrival, duration, price in TRY, partner rating (0-10) and stops per journey, plus the total count for the route.

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": {
      "origin_id": "<origin_id>",
      "destination_id": "<destination_id>",
      "date": "<date>"
    },
    "name": "obilet_search_bus_journeys"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYes
sortNoprice_asc
limitNo
origin_idYes
destination_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose meaningful behavior: the default sort (

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 structure is good: the resource/scope line comes first, then a compact per-parameter block, then the return payload. It is dense but every clause carries information; only the trailing return-field enumeration is slightly verbose given an output schema exists.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter search tool with a declared output schema, nothing an agent needs in order to call it correctly is missing: id provenance, date format, sort options, and limit bounds are all stated. Return values are described even though the output schema already covers them, which is surplus rather than a gap.

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%, so the description must compensate and it does: origin_id/destination_id are explained as bus location ids with a worked example, date is pinned to YYYY-MM-DD with a sample, sort is given all three enum values with their ordering semantics and the default, and limit is bounded to 1..24. That covers all five parameters with meaning the bare schema does not convey.

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-and-resource statement ('Bus journeys for one route + date'), so the agent immediately knows this is a route/date search over bus inventory. It explicitly points at obilet_search_locations for the id source, but it never distinguishes itself from siblings like obilet_journey_detail or obilet_price_stats, which keeps it from 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?

It gives one real prerequisite: origin_id/destination_id must come from obilet_search_locations, illustrated with a concrete İstanbul Avrupa 349 -> Ankara 356 example. Beyond that there is no when-to-use versus when-not guidance, no mention of when to prefer obilet_journey_detail (for a specific journey) or obilet_price_stats (for price trends), so the selection logic across siblings is only implied.

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