Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TRANSCAPI_API_KEYYesRequired. Your TransCAPI API key.
TRANSCAPI_BASE_URLNoOptional. Defaults to https://api.transcapi.com.https://api.transcapi.com

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_placesA

Find towns, villages, postcodes (full or partial, e.g. "S1") and stops by name. Places sharing a name are ranked by size. Give lat/lon to sort by distance from there.

nearby_stopsB

Bus, tram and rail stops within radius metres of a point, nearest first. Each has an atcocode for bus_departures and towards saying which way its buses go.

nearby_stationsA

Rail stations within radius metres of a point, with their CRS codes for rail_departures.

bus_departuresB

What is leaving (or, with board="arrivals" or "both", arriving at) a bus stop. Tracked buses have an expected time and delay_seconds; others show the timetabled time with source gtfs_scheduled.

rail_departuresA

Live trains leaving (or arriving at, with board="arrivals" or "both") a station: expected times, platforms, cancellations and delay reasons from National Rail, plus station messages. crs_code is the 3-letter code, e.g. LDS for Leeds.

train_serviceA

Every station one train calls at. For a train running today, each call has live status, expected and actual times, and the platform at its next station. Take trip_id from rail_departures.

bus_serviceA

Every stop one bus journey calls at, the days it runs, and where the bus is now if it is running. Take trip_id from bus_departures or live_buses.

live_busesA

Buses on the road within radius metres (up to 10000) of a point, nearest first, each linked to the journey it is working (trip_id) and with delay_seconds where tracked. Filter by line (e.g. "52") or operator.

disruptionsA

Planned works, incidents and line status: bus and tram across Great Britain, plus Tube, DLR, Overground, Elizabeth line and London Trams. Filter by area (lat/lon/radius), mode, operator or line. To ask what affects a particular journey, pass its route as path (an encoded polyline, e.g. a leg's leg_geometry from plan_journey): line numbers repeat across towns, so this is more reliable than line.

plan_journeyA

Public transport journeys between two points, with walking, fares and live positions of buses already running. datetime is ISO 8601 (default now); arrive_by treats it as the latest arrival. Currently covers South and West Yorkshire and West Sussex: elsewhere it returns 422 outside_coverage, which means not covered rather than no route.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 10 tools

Disambiguation5/5

Each tool targets a clearly distinct query type: place search, nearby stops/stations, mode-specific departures, live buses, disruptions, journey/service details, and journey planning. The only potential overlaps (nearby_stops vs nearby_stations, bus_departures vs live_buses) are resolved by explicit output identifiers and descriptions.

Naming Consistency4/5

All names use snake_case and are readable, with mostly noun-based resource names. Two tools use verb-led names (search_places, plan_journey), which is a minor deviation from the dominant noun-phrase pattern.

Tool Count5/5

Ten tools is well-scoped for a public transport API, covering distinct query categories without redundancy. Each tool has a clear purpose and earns its place.

Completeness4/5

The surface covers search, nearby stops/stations, departures, live vehicles, disruptions, service details, and journey planning. Minor gaps exist, such as direct lookup by stop/station identifier and dedicated tram live departures, but most workflows are supported.

Maintenance

ActivityMaintained
ResponsivenessNo issues