Skip to main content
Glama
danhussey

Transport NSW API Client MCP

by danhussey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPEN_TRANSPORT_API_KEYYesYour Transport NSW API key

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

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription
find_transport_stopsB
Find transport stops around a specific location.

Args:
    location_coord (str): Coordinates in format 'LONGITUDE:LATITUDE:EPSG:4326'
    stop_type (str): Type of stops to find: 'BUS_POINT', 'POI_POINT', or 'GIS_POINT'
    radius (int): Search radius in meters
    
Returns:
    API response with transport stops
get_transport_alertsB
Get transport alerts from the Transport NSW API.

Args:
    date (str, optional): Date in DD-MM-YYYY format. Defaults to today's date.
    mot_type (int, optional): Mode of transport type filter. Options:
        1: Train
        2: Metro
        4: Light Rail
        5: Bus
        7: Coach
        9: Ferry
        11: School Bus
    stop_id (str, optional): Stop ID or global stop ID to filter by.
    line_number (str, optional): Line number to filter by (e.g., '020T1').
    operator_id (str, optional): Operator ID to filter by.

Returns:
    dict: API response containing alerts information
get_departure_monitorA
Get real-time departure monitor information for a specific stop from the Trip Planner API.
This function uses direct HTTP requests to the Transport NSW API.

Args:
    stop_id (str): Stop ID or global stop ID
    date (str, optional): Date in DD-MM-YYYY format. Defaults to today's date.
    time (str, optional): Time in HH:MM format. Defaults to current time.
    mot_type (int, optional): Mode of transport type filter. Options:
        1: Train
        2: Metro
        4: Light Rail
        5: Bus
        7: Coach
        9: Ferry
        11: School Bus
    max_results (int, optional): Maximum number of results to return. Default is 1.
    
Returns:
    list: Simplified list of departure information

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.4/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: find_transport_stops locates stops, get_departure_monitor provides real-time departures, and get_transport_alerts retrieves service alerts. There is no overlap in functionality, and the descriptions clearly differentiate their roles.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern using snake_case: find_transport_stops, get_departure_monitor, and get_transport_alerts. The naming is predictable and readable throughout the set.

Tool Count3/5

With only 3 tools, the set feels thin for a transport API client, lacking operations like route planning, trip details, or fare information. While the tools cover basic needs, the scope suggests more comprehensive coverage would be expected.

Completeness3/5

The tools provide core functionality for stops, departures, and alerts, but there are notable gaps. Missing operations include trip planning, route searches, service status beyond alerts, and fare queries, which are typical for a transport API and could limit agent effectiveness.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources