Skip to main content
Glama

nearby

Read-only

Findet Haltestellen, POIs und Adressen im Radius um eine KOORDINATE (Schwerpunkt Hannover/Niedersachsen) — „was ist in der Nähe von <lat,lon>", „welche Haltestellen liegen um diesen Punkt". Liegt nur ein Name vor, kommt erst eine Auflösung: search_place für eine Stadt oder Region, sonst die Ortsauflösung. Pflicht: latitude, longitude, radius_m. Optional: limit (Default 10); node_types — EIN String, mehrere Arten mit Komma: 'stop', 'address', 'poi', die Sharing-Angebote 'bike_rental', 'scooter_rental', 'car_sharing', 'taxi_stand', die Abstellanlagen 'park_and_ride', 'bike_and_ride', in Südtirol Ladesäulen 'charging_station', oder 'any' ('stop,bike_rental'); include_mots (legt die bedienenden Linien über die Haltestellen-Treffer); only_available (nur Sharing-Treffer, die gerade als frei gemeldet sind, und Ladesäulen, die einen als frei gemeldeten Ladepunkt haben — UNBEKANNTE Verfügbarkeit gilt nicht als frei). Format: kompakter Einrück-Text (TOON), kein JSON. Anleitung: get_usage_guide mit tool='nearby' — die Werte im Einzelnen, was 'any' nicht abdeckt, und was ein Treffer trägt (category, modality, parking, charging, contactInfo; ein Halt in accessibility, ob er stufenfrei ist). Anti-Fab: nur die zurückgegebenen Namen, Typen, Distanzen und Verfügbarkeiten nennen; fehlt ein Feld, war es in der Quelle nicht getaggt — Öffnungszeiten und Preise stehen hier NICHT.

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>",
      "radius_m": "<radius_m>"
    },
    "name": "nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum number of results, at least 1. Default 10, values above 50 are served as 50.
formatNoAnswer serialisation: `"toon"` (default) or `"json"` — the detail is in `get_usage_guide`. **An agent leaves this out.**
latitudeYesLatitude in WGS-84 decimal degrees.
radius_mYesSearch radius in metres, more than 0.
longitudeYesLongitude in WGS-84 decimal degrees.
node_typesNoWhich kinds of place to answer with: the places the graph holds — `"stop"`, `"address"`, `"poi"` — plus the shared-mobility offers `"bike_rental"`, `"scooter_rental"`, `"car_sharing"` and `"taxi_stand"`, plus the places to leave a vehicle of one's own, `"park_and_ride"` and `"bike_and_ride"`, plus — in South Tyrol — the charging stations `"charging_station"`, or `"any"` for all of them. Several combine in ONE comma-separated string — `"stop,bike_rental"`; an array of the same tokens is read as that string. A kind outside the eleven is an argument error, not a dropped filter. `"poi"` alone also asks the backend for its tourism filter, which drops POIs whose name opens with an everyday kind (Kindergarten, Apotheke, …); `"stop,poi"` asks without it. Omit (or `"any"`) for the mixed default, in which each requested kind gets its share of `limit` and the shared-mobility offers share one between them. The two park-and-ride kinds and the charging stations are the exceptions `"any"` does NOT cover — ask for them by name; for the parking sites with a `radius_m` of a few kilometres, because they are sparse.
include_motsNo`true` overlays the serving transit lines on stop results. Default `false`, which keeps the answer small.
only_availableNoSet to `true` for „wo kann ich JETZT eines nehmen": of the shared-mobility offers, only those whose live feed reports at least one vehicle ready to be taken are answered with — and of the charging stations those with a point reported free. A place whose availability is unknown is NOT returned then, and neither is a taxi rank, which has no feed to report one. Omit (or `false`) to list every place in range. The other kinds — `"stop"`, `"address"`, `"poi"`, `"park_and_ride"`, `"bike_and_ride"` — are unaffected either way.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum number of results, at least 1. Default 10."New value: +"Maximum number of results, at least 1. Default 10, values above 50 are\nserved as 50."
    • changedInput schema / properties / node_types / description
      Previous value: -"Which kinds of place to answer with: the places the graph holds —\n`\"stop\"`, `\"address\"`, `\"poi\"` — plus the shared-mobility offers\n`\"bike_rental\"`, `\"scooter_rental\"`, `\"car_sharing\"` and `\"taxi_stand\"`,\nplus the places to leave a vehicle of one's own, `\"park_and_ride\"` and\n`\"bike_and_ride\"`, plus — in South Tyrol — the charging stations\n`\"charging_station\"`, or `\"any\"` for all of them. Several combine in ONE\ncomma-separated string — `\"stop,bike_rental\"`; an array of the same\ntokens is read as that string. A kind outside the eleven is an argument\nerror, not a dropped filter.\n`\"poi\"` alone also switches on the non-tourism filter; omit (or `\"any\"`)\nfor the mixed default, in which each requested kind gets its share of\n`limit` and the shared-mobility offers share one between them. The two\npark-and-ride kinds and the charging stations are the exceptions `\"any\"`\ndoes NOT cover — ask for them by name; for the parking sites with a\n`radius_m` of a few kilometres, because they are sparse."New value: +"Which kinds of place to answer with: the places the graph holds —\n`\"stop\"`, `\"address\"`, `\"poi\"` — plus the shared-mobility offers\n`\"bike_rental\"`, `\"scooter_rental\"`, `\"car_sharing\"` and `\"taxi_stand\"`,\nplus the places to leave a vehicle of one's own, `\"park_and_ride\"` and\n`\"bike_and_ride\"`, plus — in South Tyrol — the charging stations\n`\"charging_station\"`, or `\"any\"` for all of them. Several combine in ONE\ncomma-separated string — `\"stop,bike_rental\"`; an array of the same\ntokens is read as that string. A kind outside the eleven is an argument\nerror, not a dropped filter.\n`\"poi\"` alone also asks the backend for its tourism filter, which drops\nPOIs whose name opens with an everyday kind (Kindergarten, Apotheke, …);\n`\"stop,poi\"` asks without it. Omit (or `\"any\"`) for the mixed default, in which each requested kind gets its share of\n`limit` and the shared-mobility offers share one between them. The two\npark-and-ride kinds and the charging stations are the exceptions `\"any\"`\ndoes NOT cover — ask for them by name; for the parking sites with a\n`radius_m` of a few kilometres, because they are sparse."
    • changedInput schema / properties / radius_m / description
      Previous value: -"Search radius in metres."New value: +"Search radius in metres, more than 0."
  2. Changed2 schema fields changed
    • changedInput schema / properties / node_types / description
      Previous value: -"Which kinds of place to answer with: the places the graph holds —\n`\"stop\"`, `\"address\"`, `\"poi\"` — plus the shared-mobility offers\n`\"bike_rental\"`, `\"scooter_rental\"`, `\"car_sharing\"` and `\"taxi_stand\"`,\nplus the places to leave a vehicle of one's own, `\"park_and_ride\"` and\n`\"bike_and_ride\"`, plus — in South Tyrol — the charging stations\n`\"charging_station\"` and the taxis on the road `\"taxi\"`, or `\"any\"` for\nall of them. Several combine in ONE comma-separated string —\n`\"stop,bike_rental\"`; an array of the same tokens is read as that string.\nA kind outside the twelve is an argument error, not a dropped filter.\n`\"poi\"` alone also switches on the non-tourism filter; omit (or `\"any\"`)\nfor the mixed default, in which each requested kind gets its share of\n`limit` and the shared-mobility offers share one between them. The two\npark-and-ride kinds, the charging stations and the taxis are the\nexceptions `\"any\"` does NOT cover — ask for them by name; for the parking\nsites with a `radius_m` of a few kilometres, because they are sparse."New value: +"Which kinds of place to answer with: the places the graph holds —\n`\"stop\"`, `\"address\"`, `\"poi\"` — plus the shared-mobility offers\n`\"bike_rental\"`, `\"scooter_rental\"`, `\"car_sharing\"` and `\"taxi_stand\"`,\nplus the places to leave a vehicle of one's own, `\"park_and_ride\"` and\n`\"bike_and_ride\"`, plus — in South Tyrol — the charging stations\n`\"charging_station\"`, or `\"any\"` for all of them. Several combine in ONE\ncomma-separated string — `\"stop,bike_rental\"`; an array of the same\ntokens is read as that string. A kind outside the eleven is an argument\nerror, not a dropped filter.\n`\"poi\"` alone also switches on the non-tourism filter; omit (or `\"any\"`)\nfor the mixed default, in which each requested kind gets its share of\n`limit` and the shared-mobility offers share one between them. The two\npark-and-ride kinds and the charging stations are the exceptions `\"any\"`\ndoes NOT cover — ask for them by name; for the parking sites with a\n`radius_m` of a few kilometres, because they are sparse."
    • changedInput schema / properties / only_available / description
      Previous value: -"Set to `true` for „wo kann ich JETZT eines nehmen\": of the\nshared-mobility offers, only those whose live feed reports at least one\nvehicle ready to be taken are answered with — and of the charging\nstations those with a point reported free, of the taxis those reported\nfree. A place whose availability is unknown is NOT returned then, and\nneither is a taxi rank, which has no feed to report one. Omit (or\n`false`) to list every place in range. The other kinds — `\"stop\"`,\n`\"address\"`, `\"poi\"`, `\"park_and_ride\"`, `\"bike_and_ride\"` — are\nunaffected either way."New value: +"Set to `true` for „wo kann ich JETZT eines nehmen\": of the\nshared-mobility offers, only those whose live feed reports at least one\nvehicle ready to be taken are answered with — and of the charging\nstations those with a point reported free. A place whose availability\nis unknown is NOT returned then, and neither is a taxi rank, which has\nno feed to report one. Omit (or\n`false`) to list every place in range. The other kinds — `\"stop\"`,\n`\"address\"`, `\"poi\"`, `\"park_and_ride\"`, `\"bike_and_ride\"` — are\nunaffected either way."
  3. Changed2 schema fields changed
    • changedInput schema / properties / node_types / description
      Previous value: -"Which kinds of place to answer with: the places the graph holds —\n`\"stop\"`, `\"address\"`, `\"poi\"` — plus the shared-mobility offers\n`\"bike_rental\"`, `\"scooter_rental\"`, `\"car_sharing\"` and `\"taxi_stand\"`,\nplus the places to leave a vehicle of one's own, `\"park_and_ride\"` and\n`\"bike_and_ride\"`, or `\"any\"` for all of them. Several combine in ONE\ncomma-separated string — `\"stop,bike_rental\"`; an array of the same\ntokens is read as that string. A kind outside the ten is an argument\nerror, not a dropped filter. `\"poi\"` alone also switches on the\nnon-tourism filter; omit (or `\"any\"`) for the mixed default, in which each\nrequested kind gets its share of `limit` and the shared-mobility offers\nshare one between them. The two park-and-ride kinds are the exception\n`\"any\"` does NOT cover — ask for them by name, and with a `radius_m` of a\nfew kilometres, because such sites are sparse."New value: +"Which kinds of place to answer with: the places the graph holds —\n`\"stop\"`, `\"address\"`, `\"poi\"` — plus the shared-mobility offers\n`\"bike_rental\"`, `\"scooter_rental\"`, `\"car_sharing\"` and `\"taxi_stand\"`,\nplus the places to leave a vehicle of one's own, `\"park_and_ride\"` and\n`\"bike_and_ride\"`, plus — in South Tyrol — the charging stations\n`\"charging_station\"` and the taxis on the road `\"taxi\"`, or `\"any\"` for\nall of them. Several combine in ONE comma-separated string —\n`\"stop,bike_rental\"`; an array of the same tokens is read as that string.\nA kind outside the twelve is an argument error, not a dropped filter.\n`\"poi\"` alone also switches on the non-tourism filter; omit (or `\"any\"`)\nfor the mixed default, in which each requested kind gets its share of\n`limit` and the shared-mobility offers share one between them. The two\npark-and-ride kinds, the charging stations and the taxis are the\nexceptions `\"any\"` does NOT cover — ask for them by name; for the parking\nsites with a `radius_m` of a few kilometres, because they are sparse."
    • changedInput schema / properties / only_available / description
      Previous value: -"Set to `true` for „wo kann ich JETZT eines nehmen\": of the\nshared-mobility offers, only those whose live feed reports at least one\nvehicle ready to be taken are answered with. A station whose\navailability is unknown is NOT returned then, and neither is a taxi\nrank, which has no feed to report one. Omit (or `false`) to list every\nplace in range. The other kinds — `\"stop\"`, `\"address\"`, `\"poi\"`,\n`\"park_and_ride\"`, `\"bike_and_ride\"` — are unaffected either way."New value: +"Set to `true` for „wo kann ich JETZT eines nehmen\": of the\nshared-mobility offers, only those whose live feed reports at least one\nvehicle ready to be taken are answered with — and of the charging\nstations those with a point reported free, of the taxis those reported\nfree. A place whose availability is unknown is NOT returned then, and\nneither is a taxi rank, which has no feed to report one. Omit (or\n`false`) to list every place in range. The other kinds — `\"stop\"`,\n`\"address\"`, `\"poi\"`, `\"park_and_ride\"`, `\"bike_and_ride\"` — are\nunaffected either way."
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare read-only, non-destructive, open-world behavior, and the description adds substantial context beyond them: output is compact TOON indented text rather than JSON, unknown availability is NOT treated as free, taxi ranks are excluded from availability filtering, and opening hours and prices are explicitly absent. It also names what each hit carries (category, modality, parking, charging, contactInfo, accessibility) and adds an anti-fabrication rule.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and prerequisites are front-loaded, but the middle section re-enumerates the entire node_types vocabulary already documented in the schema, and heavy bold markup plus long parentheticals make it dense. Much of it earns its place, yet the schema duplication is avoidable bloat.

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 an eight-parameter, no-output-schema tool this covers everything an agent needs: required vs optional parameters, output serialization, per-hit fields, availability edge cases, explicit data gaps (no hours or prices), and a pointer to the deeper usage guide.

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?

Schema coverage is already 100%, but the description still adds real meaning: node_types must be ONE comma-separated string, 'any' does not cover park_and_ride/bike_and_ride/charging_station, the mixed default splits `limit` per kind, and sparse parking kinds need a radius of a few kilometres. It mostly restates the schema's enumeration list, which keeps it from a 5.

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?

Opens with a specific verb and enumerates the resources returned (Haltestellen, POIs, Adressen) plus the scope constraint (radius um eine Koordinate, Schwerpunkt Hannover/Niedersachsen). It also distinguishes itself from search_place, which handles the name-only case, so an agent can pick between them without opening either schema.

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?

Gives an explicit routing rule: if only a name is available, resolve first via `search_place` for a city/region, otherwise the local resolution. It also steers agents to `get_usage_guide` with tool='nearby' for details. It does not contrast against other spatial siblings such as reverse_geocode, but the primary when-to-use case is covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources