Skip to main content
Glama

get_bus_schedule

Read-onlyIdempotent

Get upcoming bus departures for a route, stop, or both.

Returns the next departures from now (future only for today).
Provide at least route_number or stop_id. Get stop_id from
get_nearest_bus_stop, route_number from get_bus_routes.

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": "get_bus_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoDate in YYYY-MM-DD format (default: today).
limitNoMax departures to return. Use 0 for full day schedule.
stop_idNoBus stop ID (obtain from get_nearest_bus_stop).
directionNoFilter by destination name, e.g. 'Kópavogur', 'Mjódd', 'Eiðistorg'.
from_timeNoStart time filter in HH:MM format (default: now).
route_numberNoRoute number, e.g. '1', '6', '15'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile needs no restating. The description adds real behavioral value beyond them: results are future-only and start from 'now' for today, and at least one of two parameters must be supplied. It leaves the interaction between an explicit date and the 'future only for today' rule unstated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose before the behavior caveat and prerequisites. No filler, no restatement of the title, and the quote-wrapped formatting does not dilute the content.

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 an output schema present, return values need no explanation, and annotations cover safety, so the description's remaining job is scope and preconditions — both covered. The one residual gap is what happens to the 'from now' default when a future date is supplied.

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 coverage is 100% with descriptions for every one of the six parameters, so the schema carries the semantics. The description only echoes the at-least-one constraint on route_number/stop_id and adds no format or default detail beyond what the schema already declares (date default, limit=0 behavior, HH:MM from_time).

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 and resource ('Get upcoming bus departures') plus the three ways it can be scoped (route, stop, or both), which lets an agent distinguish it from ID-lookup siblings like get_nearest_bus_stop and get_bus_routes. It does not contrast itself with get_live_buses, so the boundary against real-time vehicle tracking is left 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?

Gives a concrete precondition ('Provide at least route_number or stop_id') and routes the agent to the correct upstream call for each identifier, which is exactly the guidance needed before invoking. It stops short of stating when-not to use it or naming a preferred alternative for a specific scenario.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources