Skip to main content
Glama
maxim75

TfNSW Trip Planner MCP Server

by maxim75
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

find_stop

Search by place name to get the stop, station, wharf, or address ID required for trip planning and departure tools. Filter by location type for precise results.

Instructions

Search for stops, stations, wharves, points of interest and addresses by name.

Use this to turn a place name into the stop ID that the trip planning and
departure tools require.

Args:
    query: What to search for, e.g. "Circular Quay" or "Town Hall Station".
    location_type: Restrict results — "any", "stop", "platform", "poi",
        "address", "street" or "locality".
    limit: Ask the TfNSW API to return at most this many matches. Unlike
        max_results on the capped tools, this bounds the upstream query
        rather than truncating a fetched list, so `count` is exact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
queryYes
location_typeNoany

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior3/5

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

The description discloses some behavioral detail (e.g., limit bounds the upstream query so count is exact) but does not mention side effects, permissions, or rate limits. With no annotations to rely on, the description carries the full burden but only partially covers behavioral traits.

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?

The description is compact and well-organized, with a clear opening sentence, a purpose statement, and a structured list of parameter explanations. No redundant or irrelevant information is present.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple search tool, the description fully covers the required input and purpose. The existence of an output schema means return values need not be described, and the note about 'count is exact' provides a relevant behavioral detail without over-explaining.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All three parameters (query, location_type, limit) are explicitly described with examples and allowed values, compensating fully for the lack of schema descriptions. The explanation of limit's distinct behavior adds meaningful context beyond the parameter names.

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?

The description clearly states the verb 'Search' and the resource 'stops, stations, wharves, points of interest and addresses', and explains the primary purpose of converting a place name into a stop ID for use by trip planning and departure tools. This makes the tool's function unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit guidance on when to use the tool ('Use this to turn a place name into the stop ID...') and includes a helpful note about the limit parameter differing from max_results in other tools. This gives the agent clear direction on selection and parameter behavior.

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

Deploy Server

Other Tools