Skip to main content
Glama

get_bus_routes

Read-onlyIdempotent

Find Straeto bus routes serving an area or connecting two areas.

Returns route number, name, and key_stops with coordinates for each route.
key_stops contain name, latitude, longitude — render as a route line on a map.
Use the route number in get_bus_schedule or get_live_buses.

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

Input Schema

NameRequiredDescriptionDefault
areaNoArea or street name to search for routes, e.g. 'Laugavegur', 'Háteigsvegur', 'Keflavík'.
limitNoMaximum number of routes to return (default 20, cap 100). Results are sliced from the front of the matched list — narrow with ``area`` / ``destination_area`` if you need a specific corridor.
latitudeNoLocation latitude (WGS84) for proximity-based route lookup.
longitudeNoLocation longitude (WGS84) for proximity-based route lookup.
destination_areaNoDestination area for finding connecting routes, e.g. 'Laugardalslaug', 'Kópavogur'.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds genuine value by describing the return payload (route number, name, key_stops with coordinates) and a rendering hint for map lines. With annotations carrying the behavioral burden, this is solid but not rich — it says nothing about ordering, result completeness, or what happens when an area matches nothing.

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?

Four short lines, front-loaded with purpose, then return shape, then a rendering hint, then the follow-up tool. Every sentence carries usable information and nothing is wasted.

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?

Covers purpose, return shape, and next-step routing, and an output schema exists so detailed return documentation is unnecessary. The one real gap is that the latitude/longitude proximity-lookup mode — a distinct way to call this 5-parameter tool — is never mentioned in the description, so an agent reading only the prose would miss it.

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 the baseline is 3; the description earns an extra point by making the area vs. destination_area distinction semantically explicit ('serving an area or connecting two areas'), which is the key modeling decision an agent must get right. It does not mention the latitude/longitude proximity mode or the limit slicing behavior, leaving those entirely to 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 (find) plus resource (Straeto bus routes) and enumerates both operational modes: routes serving an area, or routes connecting two areas. An agent can immediately tell this apart from get_bus_schedule and get_live_buses, which the description names as downstream consumers.

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?

Implicitly clarifies the two usage modes (single area lookup vs. origin/destination connection) and explicitly routes the agent forward by saying to use the returned route number in get_bus_schedule or get_live_buses. It does not state when to prefer this over get_nearest_bus_stop for proximity questions, though the latitude/longitude parameters suggest an overlap the description never addresses.

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