Skip to main content
Glama

get_live_buses

Read-onlyIdempotent

Get real-time Straeto bus positions across Reykjavik and Iceland.

Each vehicle in `vehicles` contains:
  - latitude, longitude: WGS84 GPS position
  - route_number, route_id, bearing, speed_kmh
Render vehicles as markers on a map using their coordinates.

When a route is specified, `route_polyline` contains the route's geographic
path as a list of {latitude, longitude} points — render as a line on the map.

`live_map_url` is a clickable link to an interactive browser map.
Always present both the map rendering and the live_map_url link.

Tip: call get_bus_routes first to find the route number, then pass it
here to get a focused map for that specific route.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of vehicles to return.
routeNoRoute number to track, e.g. '1', '6'. Omit for all active buses.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, and the description adds real value on top: it explains that `route_polyline` only appears when a route is specified and instructs the agent to always surface both the map rendering and the live_map_url link. That presentational obligation is behavior the agent would not infer from annotations.

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?

Front-loaded with purpose, then organized into field list, rendering instructions, and a tip. Most sentences earn their place, though the per-field bullet list partially duplicates the output schema and adds some length.

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 fully explained, yet the description covers conditional fields and presentation requirements well. Only minor gaps remain, such as no mention of what an empty `vehicles` list means or freshness/latency of the real-time positions.

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 100%, so parameter definitions are already handled. The description still adds meaning beyond the schema by tying the `route` parameter to the conditional presence of `route_polyline`, which is not stated in the schema. The `limit` parameter gets no additional treatment, but it is fully documented in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Get real-time Straeto bus positions') plus geographic scope (Reykjavik and Iceland). This clearly separates it from siblings like get_bus_routes (route catalog) and get_nearest_bus_stop (stop lookup).

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?

Provides explicit chaining guidance: call get_bus_routes first to obtain a route number, then pass it here for a focused map. It also notes that omitting the route returns all active buses. It does not address when to prefer a different sibling for proximity questions, so it stops short of full when/when-not coverage.

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