properties_transport_nearbyNearest train / tram / bus / ferry stop to the property, per mode,
with distance. Widen radius_m for the nearest station beyond 1km.
Price: 5¢ per call.
| Name | Required | Description | Default |
|---|---|---|---|
| gnaf_id | Yes | ||
| radius_m | No | Search radius in metres (100–5000, default 1000). |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -{
- "properties": {
- "available": {
- "anyOf": [
- {
- "type": "boolean"
- },
- {
- "type": "null"
- }
- ],
- "description": "`false` on no-data responses. Omitted on success — branch on `data !== null` if you want a single discriminator.",
- "title": "Available"
- },
- "data": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "Nearest public-transport stop per mode within the radius.",
- "example": {
- "center_lat": -33.802479,
- "center_lng": 151.219715,
- "counts": {
- "bus": 6,
- "ferry": 0,
- "train": 0,
- "tram": 0
- },
- "gnaf_id": "GANSW704360755",
- "nearest": {
- "bus": {
- "distance_m": 130,
- "label": "Bus stop",
- "lat": -33.8031,
- "lng": 151.2201
- }
- },
- "radius_m": 1000
- },
- "properties": {
- "center_lat": {
- "description": "Property latitude (WGS84).",
- "title": "Center Lat",
- "type": "number"
- },
- "center_lng": {
- "description": "Property longitude (WGS84).",
- "title": "Center Lng",
- "type": "number"
- },
- "counts": {
- "additionalProperties": {
- "type": "integer"
- },
- "description": "Count per mode within the radius (train / tram / bus / ferry).",
- "title": "Counts",
- "type": "object"
- },
- "gnaf_id": {
- "description": "GNAF property identifier.",
- "title": "Gnaf Id",
- "type": "string"
- },
- "nearest": {
- "additionalProperties": {
- "anyOf": [
- {
- "additionalProperties": true,
- "description": "The nearest stop/station of one mode.",
- "properties": {
- "distance_m": {
- "anyOf": [
- {
- "type": "integer"
- },
- {
- "type": "null"
- }
- ],
- "description": "Straight-line distance from the property, metres.",
- "title": "Distance M"
- },
- "label": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Mode label: Train station / Tram stop / Bus stop / Ferry terminal.",
- "title": "Label"
- },
- "lat": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Latitude (WGS84).",
- "title": "Lat"
- },
- "lng": {
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "description": "Longitude (WGS84).",
- "title": "Lng"
- },
- "name": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Stop / station name (blank for bus & tram stops).",
- "title": "Name"
- }
- },
- "title": "TransportStop",
- "type": "object"
- },
- {
- "type": "null"
- }
- ]
- },
- "description": "Nearest stop per mode; null when none falls inside the radius.",
- "title": "Nearest",
- "type": "object"
- },
- "radius_m": {
- "description": "Search radius applied, metres.",
- "title": "Radius M",
- "type": "integer"
- }
- },
- "required": [
- "gnaf_id",
- "center_lat",
- "center_lng",
- "radius_m",
- "counts",
- "nearest"
- ],
- "title": "TransportNearby",
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "description": "The endpoint's payload, or `null` when Microburbs has no value."
- },
- "message": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Human-readable explanation. Omitted on success.",
- "title": "Message"
- },
- "reason": {
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "description": "Machine-readable slug naming the no-data condition (e.g. `no_avm_for_GANSW704074813`). Stable per endpoint. Omitted on success.",
- "title": "Reason"
- }
- },
- "title": "ApiResponse[TransportNearby]",
- "type": "object",
- "x-fastmcp-top-level-schema": "ApiResponse_TransportNearby_"
-}New value: +nullDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. The description adds the cost (5¢ per call) and a practical radius-widening tip, which is useful context. It does not describe output format or pagination, but the annotation coverage lowers the bar.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short sentences, each with a distinct purpose: stating the core function, providing a parameter tip, and giving pricing. The description is front-loaded with the main purpose and contains zero fluff. Excellent economy of words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter read-only tool with rich annotations, the description covers the essential behavior and cost. It is missing explicit usage guidance vs siblings like properties_amenities_nearby, and it does not mention distance units or output shape. Overall adequate but not thorough.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already documents radius_m fully (range and default), and the description adds a useful tip for when to widen it. However, the required gnaf_id has no schema description and the tool description does not clarify what it is or how to obtain it, leaving a significant gap for an agent trying to invoke the tool correctly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb ('nearest') and resource ('train / tram / bus / ferry stop') and clarifies output ('per mode, with distance'). It distinguishes from siblings like properties_amenities_nearby or properties_schools_nearby by the transport resource. However, it doesn't explicitly name any sibling alternative, which is a minor gap.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to choose this tool over its many siblings. The only usage hint is about widening radius_m for distances beyond 1km, which is a parameter tip rather than tool-selection advice. There is no mention of when not to use it or what alternatives exist.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.