Mobiliteit.lu MCP

Find nearby public transport stops

find_nearby_stops

Locate public transport stops near a WGS84 coordinate in Luxembourg, returning stop IDs for departures or departure-change subscriptions.

Instructions

Find public transport stops near a WGS84 coordinate in Luxembourg. Use the returned stop id with get_departures or subscribe to its departure resource.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "find_nearby_stops"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`language`	No		fr
`latitude`	Yes	Latitude in degrees
`longitude`	Yes	Longitude in degrees
`radiusMeters`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.1Oct 19, 2026

TDQS

A3.9/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose that the result is usable as a stop id and that a departure resource exists, but it says nothing about result ordering, how radius/limit shape the answer, rate limits, or auth requirements. Adequate but thin for an annotation-free tool.

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?

Two tight sentences, front-loaded with the core action and scope, then the follow-up usage. No filler, nothing redundant.

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?

With no output schema and no annotations, the description does the important work of identifying the geographic domain, the coordinate system, and the primary return value (stop id) plus its downstream use. It stops short of explaining radius/limit semantics, but is otherwise sufficient for a straightforward lookup.

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

Parameters2/5

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

Schema coverage is only 40% — limit, language, and radiusMeters have no descriptions anywhere, and the description adds no parameter guidance at all (latitude/longitude and WGS84 are already in the schema). With five parameters and low coverage, the description should compensate and does not.

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 and resource ('Find public transport stops') with both the geographic scope ('near a WGS84 coordinate') and the coverage area ('in Luxembourg'). It also implicitly distinguishes itself from the sibling by describing its role as the stop-discovery step that feeds get_departures.

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?

The second sentence gives clear workflow context: take the returned stop id into get_departures or subscribe to its departure resource. That routes the agent to the correct alternative, though it never states when not to use this tool (e.g., if you already have a stop id) — a minor gap given there is only one sibling.

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

Deploy Server