TfNSW Trip Planner MCP Server

Overview Schema Source Related Servers Discussions Admin

get_vehicle_positions

Retrieve live GPS locations of vehicles on a chosen TfNSW mode. Use it to see exactly where buses, trains, ferries, or light rail are right now.

Instructions

Fetch live GPS positions of vehicles currently running on a network.

Unlike the other tools, which return timing estimates, this returns where
each vehicle physically is. Note this feed is a separate product on the
TfNSW Open Data portal — your API key must be subscribed to it as well.

Feeds can carry thousands of vehicles, so results are capped: `count` is the
true feed size and `returned` is how many are included.

Args:
    mode: Which feed to read. One of "buses", "sydneytrains", "metro",
        "nswtrains", "ferries/sydneyferries", "lightrail/cbdandsoutheast",
        "lightrail/innerwest", "lightrail/newcastle",
        "lightrail/parramatta".
    max_results: Maximum vehicles to return.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mode`	Yes
`max_results`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A4.3/5.0

Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses subscription requirements and the capping behavior with count/returned distinction, which are important runtime behaviors not inferable from the schema.

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?

Structured with clear sections. Contains a few extra phrases like 'Unlike...' and 'Note...' that add context but could be tightened. Overall efficient and well-organized.

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 format is not required. The description still mentions the count/returned fields and the cap, which are important contextual details. Missing explicit mention of coordinate units or timestamp format, but not critical.

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?

The schema provides basic types but lacks enumerations for mode. The description adds the explicit list of allowed modes and explains max_results default, which adds meaning beyond the raw schema. Slight redundancy but helpful.

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?

Clearly states the verb 'Fetch' and the resource 'live GPS positions of vehicles'. Explicitly contrasts with sibling tools that return timing estimates, making its unique purpose unambiguous.

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?

Mentions that it is a separate product requiring subscription and that results are capped. Implies usage when location data is needed, though it does not explicitly enumerate alternative tools. Slight room for more direct 'use when' guidance.

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

Deploy Server