Skip to main content
Glama

Bus price calendar

mb_bus_price_calendar
Read-onlyIdempotent

Compare daily bus seat prices for a route over a date range, leaving out days with no buses or tickets not yet on sale.

Instructions

Cheapest bus seat per day for a route; days without buses (or not on sale yet) are left out.

Then mb_search_buses for the chosen 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": {
      "origin": "<origin>",
      "destination": "<destination>"
    },
    "name": "mb_bus_price_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of days to cover.
seatsNoSeats needed.
originYesBus city or terminal id from mb_find_place(mode='bus'), e.g. 11320000 (Tehran).
start_dateNoFirst day YYYY-MM-DD; default today.
destinationYesBus city or terminal id from mb_find_place(mode='bus'), e.g. 11320000 (Tehran).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.5.0
    • changedInput schema / properties / destination / description
      Previous value: -"Bus city or terminal id from mb_find_place(mode='bus'), e.g. 11320000 (Tehran, all terminals) or 31310000 (Mashhad)."New value: +"Bus city or terminal id from mb_find_place(mode='bus'), e.g. 11320000 (Tehran)."
    • changedInput schema / properties / origin / description
      Previous value: -"Bus city or terminal id from mb_find_place(mode='bus'), e.g. 11320000 (Tehran, all terminals) or 31310000 (Mashhad)."New value: +"Bus city or terminal id from mb_find_place(mode='bus'), e.g. 11320000 (Tehran)."
    • removedInput schema / properties / start_date / anyOf
      Removed value: -[
      -  {
      -    "format": "date",
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • changedInput schema / properties / start_date / description
      Previous value: -"First day YYYY-MM-DD, e.g. '2026-10-10'; default today."New value: +"First day YYYY-MM-DD; default today."
    • addedInput schema / properties / start_date / format
      Added value: +"date"
    • addedInput schema / properties / start_date / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedInput schema / title
      Removed value: -"mb_bus_price_calendarArguments"
  2. Changed6 schema fields changedv0.3.0
    • removedInput schema / properties / days / title
      Removed value: -"Days"
    • removedInput schema / properties / destination / title
      Removed value: -"Destination"
    • removedInput schema / properties / origin / title
      Removed value: -"Origin"
    • removedInput schema / properties / seats / title
      Removed value: -"Seats"
    • removedInput schema / properties / start_date / title
      Removed value: -"Start Date"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "title": "mb_bus_price_calendarDictOutput",
      -  "type": "object"
      -}New value: +null
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive behavior, so the safety profile needs no restating. The description adds real behavioral value beyond them: the result is a per-day minimum price, and days with no service or not yet on sale are silently omitted, which an agent must know to avoid misreading gaps as errors. It does not mention currency, timezone, or how the default 30-day window is anchored.

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 short sentences with no filler, and the return-value/omission rule is front-loaded ahead of the next-step pointer. The second sentence is a fragment beginning with 'Then', which reads slightly telegraphic but costs nothing in clarity.

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?

With five parameters and no output schema, the description must carry the return shape, and it does by specifying cheapest price per day plus the omission rule. No output schema exists, so return values are only partially covered (no currency or calendar span), but an agent has enough to call it correctly and interpret gaps.

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 100%, and the schema already documents origin/destination ids, days, seats, and start_date format. The description adds no parameter-level meaning beyond that, so the baseline 3 applies. It also does not clarify that 'cheapest bus seat' is conditioned on the seats parameter.

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 names the resource and the exact value returned ('cheapest bus seat per day for a route'), which is more specific than the title 'Bus price calendar'. It also conveys a scope rule: days with no buses or not yet on sale are omitted. It stops short of naming its closest sibling, mb_train_price_calendar, so differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly positions the tool as the first step in a two-step flow: read the calendar first, then call mb_search_buses for the chosen day. That is actionable routing guidance. It does not state when to avoid this tool (e.g. when a single-day search is already known, or how mb_bus_seats fits), so it lacks explicit exclusions.

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