Skip to main content
Glama
maxim75

TfNSW Trip Planner MCP Server

by maxim75
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

best_stop

Resolve a place name to its single best-matching stop ID, returning null if no match exists.

Instructions

Return only the single best-matching location for a name.

A shortcut for find_stop when you just need one stop ID and do not want to
weigh alternatives. Returns `{"location": null}` if nothing matches.

Args:
    query: The place name to resolve, e.g. "Bondi Junction".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

No annotations are present, so the description carries the full burden. It discloses the return behavior (including null case) but does not explicitly state side effects or whether the operation is read-only; however, the wording strongly implies a lookup.

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 succinct, with no filler, and front-loads the core purpose while keeping parameter details in a natural place.

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?

For a simple lookup tool, it covers the main context: purpose, when to use, parameter meaning, and return null behavior. It does not mention edge cases or errors, but the scope is narrow enough that this is not a significant gap.

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 only a title for 'query', but the description adds a meaningful explanation with an example ('The place name to resolve, e.g. "Bondi Junction"'), compensating for the otherwise bare 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 ('Return'), a specific resource ('single best-matching location for a name'), and explicitly contrasts with the sibling 'find_stop', so its purpose is immediately clear.

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?

Explicitly says when to use it ('when you just need one stop ID and do not want to weigh alternatives') and names the alternative tool 'find_stop', leaving no ambiguity.

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