Skip to main content
Glama

show_connections_slim

Read-only

Dieselbe Verbindungs-Ansicht wie show_connections, nur schlank ausgeliefert: das Kartenwerk lädt die Ansicht als Skript, statt es mitzubringen. Nimm dies nur, wenn ausdrücklich nach der schlanken Auslieferung gefragt wird — sonst show_connections. Sonst unverändert: plant die Fahrt wie connections und liefert sie zusätzlich als Ansicht aus. Pflicht sind BEIDE Endpunkte, wie dort: origin_id UND destination_id — oder die vier Koordinaten-Felder; render_payload entfällt. Die Verlässlichkeit der Umstiege nur auf Wunsch, wie dort: change_reliability: true oder max_miss_risk. Carsharing nur auf Wunsch, wie dort: car:sharing in access_modes/egress_modes, ein Stationsauto dazu mit stay_minutes. Der Antwort-Text ist der von connections — Abfahrt und Ankunft aus departs/arrives, nach einem Fußweg die erste Fahrt aus firstRide; die Rohdaten daneben tragen nur die Felder, die die Ansicht zeichnet, in Ortszeit wie der Text, ihr Kartenverlauf davon im _meta. Anleitung: get_usage_guide mit tool='connections'. Anti-Fab: Linien, Zeiten, Halte und Gleise ausschließlich aus dem Output dieses Aufrufs.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "show_connections_slim"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoDie Sprache der Namen: `'de'` (Vorgabe), `'it'`, `'fr'`, auch mit Region (`'de-CH'`).
timeNoISO 8601; without an offset local time in Berlin (`"2026-11-06T08:30"`). Omit to plan from now. Resolve a spoken time with the time tool rather than computing one.
viasNoZwischenhalte in Reiserichtung, höchstens 4, statt `via_id`/`via_lat`/`via_lon`: je `id`+`type` (wie ein Endpunkt) oder `lat`+`lon`, dazu `kind`, `stay_minutes`.
limitNoMaximum number of journeys, at least 1. Default 5, values above 15 are served as 15.
modesNoTransport-mode restriction, not a preference: nothing outside the list is planned. The footpath always stays allowed — the way to, from and between stops goes on foot — while `["foot"]` on its own plans no ride at all. Entries: `"bike"`, `"bike_rental"`, `"foot"`, `"car"`, `"taxi"`, `"scooter"`, `"transit"`, `"bus"`, `"tram"`, `"rail"`, `"subway"`, `"ferry"`, `"air"` (flights); several combine. An entry outside that list is an argument error, not a dropped filter. Omitted or empty = all standard transit modes, the ferry included, and a flight where one arrives sooner; `"transit"` = the same without flights. Set only when the user insists on a mode; the guide has the vocabulary and the traps.
formatNoAnswer serialisation: `"toon"` (default) or `"json"` — the detail is in `get_usage_guide`. **An agent leaves this out.**
via_idNoIntermediate stop the route must pass through („über X"), as an id in the same form as `origin_id`. The route is then planned A → via → B.
not_viaNoHalt-Ids wie `origin_id`, die keine Verbindung berührt.
via_latNoVia latitude, for an intermediate address or POI without an id. Goes with `via_lon`.
via_lonNoVia longitude. Goes with `via_lat`.
extendedNo`true` keeps the map data in the text: every stop's coordinate, every leg's polyline, and the whole stop sequence with them — for an application that DRAWS the route, at two to three times the answer. A chat client leaves it off.
via_typeNoWhat `via_id` is. Same values as `origin_type`.
cancelledNo`exclude` (Default), `include` (dazu `broken_journeys` mit Grund) oder `mark` (dazu jeder Halt beurteilt und wo neu zu suchen ist).
origin_idNoOrigin id: the resolver's `main` id as handed out — for a stop a DHID (`de:NNNNN:NNN`, `at:…`, `ch:…`, `it:…`) or a station id (`Parentch:1:sloid:3000`), else the address or POI id. Resolve the place first — a name here is an argument error.
verbosityNoHow much of each journey comes back: `"compact"` (default — everything an answer is cited from) or `"full"` (adds the stops in between). A third word is an argument error, not the default.
only_linesNoLine whitelist. Entries are line tokens as printed on the vehicle (`"6"`, `"U3"`); a journey is kept only if every transit leg uses one of them.
origin_latNoOrigin latitude, WGS-84 decimal degrees — the fallback when no id is at hand, and the one retry worth making when a resolved id is refused.
origin_lonNoOrigin longitude. Goes with `origin_lat`.
walk_speedNoWalking speed of the foot legs in metres/second, between 0.3 and 3 m/s — outside that it is an argument error. Default ≈1.33, slow ≈0.7, brisk ≈2.0. Overrides the walk speed of `accessibility_profile`.
origin_typeNoWhat `origin_id` is: `"stop"` (default), `"address"` or `"poi"`. The backend resolves an address or a POI to its real name from the id.
prefer_flatNo`true` plant die hügel-ärmste statt der sonst gewählten Rad-Route: die Suche gewichtet die Steigung und nimmt dafür Umwege in Kauf, nur auf Rad-Abschnitten. Keine Zusage — ohne flachere Alternative kommt dieselbe Route; die Höhenmeter der Antwort sagen es. Wann setzen: die Anleitung.
taxi_pickupNoWo das Taxi die Fahrten trifft: `door` (Default, am Halt) oder `rank` (am Taxistand).
access_modesNoWeg zur ersten Haltestelle: Einträge `fahrzeug[:own|sharing][:only|prefer]`, Fahrzeug `walk`, `bike`, `scooter`, `car`, `taxi`; `own`/`sharing` eigenes/geliehenes (sonst gleich wessen); `only` nur damit, `prefer` (Default) neben dem Fußweg.
egress_modesNoWie `access_modes`, für den Weg von der letzten Haltestelle.
no_change_atNoHalt-Ids wie `origin_id`, an denen keine Verbindung umsteigt.
stay_minutesNoAufenthalt am Ziel, 0–1440 Minuten: ein Leihfahrzeug mit fester Station fährt damit hin und zurück; ohne ihn keins.
bike_carriageNoDas Rad fährt auf jeder Fahrt mit: `true` nur auf Fahrten, die es bekanntlich mitnehmen, `'allow_unknown'` auch ohne Angabe.
cycling_speedNoRad-Tempo in Metern/Sekunde, 1 bis 12 — außerhalb ein Argument-Fehler. Überschreibt `cycling_profile`. Richtwerte: Familie ≈2.8, normal ≈5, Pedelec ≈6.5.
exclude_linesNoLine blacklist, same token form as `only_lines`. A journey is dropped if any transit leg uses one of them.
max_miss_riskNoAb welchem Risiko, einen Umstieg zu verpassen, eine verlässlichere Alternative daneben steht: ein Anteil von 0 bis 1 (`0.1` = 10 %), auch ohne `change_reliability`. Weggelassen: keine Alternative.
max_transfersNoUpper bound on interchanges: `0` = direct, up to `3`; another number is an argument error. Omit unless the user constrains transfers: the backend then derives the search depth from the trip's air-line distance and escalates it when the first attempt finds nothing, so omitting never loses a connection.
submodes_denyNoFine submode blacklist, same vocabulary as `submodes_allow`. A journey is dropped if any transit leg matches one.
destination_idNoDestination id. Same form as `origin_id`.
submodes_allowNoFine submode whitelist — finer than `modes`, which only separates bus/tram/rail/subway. Entries: `"sbahn"`, `"regionalbahn"`, `"ice"`, `"ic"`, `"ir"`, `"nj"`, `"fernverkehr"`, `"stadtbahn"`, `"ubahn"`, `"bus"`, `"regionalbus"`, `"stadtbus"`, `"flug"` (flights). A journey is kept only if every transit leg matches one.
cycling_profileNoWer auf dem Rad sitzt, und damit das Tempo der Rad-Abschnitte: `family` (mit kleinen Kindern), `normal` (Default, unverändert) oder `ebike` (Pedelec). Ein anderer Name ist ein Argument-Fehler.
destination_latNoDestination latitude. Same use as `origin_lat`.
destination_lonNoDestination longitude. Goes with `destination_lat`.
is_arrival_timeNo`true` reads `time` as the desired ARRIVAL time instead of the departure time.
max_walk_metersNoCap on the summed walking DISTANCE in metres. Works like `max_walk_minutes`, on the metres walked.
destination_typeNoWhat `destination_id` is. Same values as `origin_type`.
max_walk_minutesNoCap on the summed walking TIME in minutes, at least 1: every journey of the answer keeps to it.
mobility_profileNoHow the first and the last mile may be covered, by name: `"transit"` (default — both ends on foot), `"transit_plus_sharing"` (a shared bike), `"door_to_door"` (being driven), `"park_and_ride"` or `"bike_and_ride"` (one's OWN car or bicycle, left where the transit leg starts). Another name is an argument error. It widens those two ends, restricts no ride and promises nothing. When to set which, and how it composes with `modes`, is in the usage guide.
change_reliabilityNo`true` nur, wenn der Nutzer nach der Verlässlichkeit der Umstiege fragt: dann sagen `change` und `reliability`, wie oft die Umstiege klappten. Weggelassen: nichts davon, außer mit `max_miss_risk`.
include_rental_bikeNo`true` adds a rental-bike leg (park-and-bike / station rental). Equivalent to naming `"bike"` in `modes` together with a transit mode.
max_walk_from_originNoHöchstens so weit zu Fuß vom Start zur ersten Haltestelle, Meter über die Straße: ganze Meter von 1 bis 5000; darüber gilt 5000, und `not_considered` sagt es.
accessibility_profileNoMobility profile by name: `"Standard"` (default), `"WheelchairRobust"`, `"WalkerComfort"`, `"PramComfort"`, `"VisuallyImpaired"` or `"IndividualComfort"`. Each bundles its accessibility constraints and walk speed; another name is an argument error. Where the step-free three (wheelchair, walker, pram) find no stated step-free ride, `accessibility_routing` says what the journeys beside it are; these three and `VisuallyImpaired` note on a walk what the map knows (`additionalInfos.walkNotes`). What each profile constrains is in the usage guide.
accessibility_unknownNoNur mit `WheelchairRobust`/`WalkerComfort`/`PramComfort`: `refuse` nimmt nur als stufenfrei Ausgewiesenes, `admit` auch, worüber nichts bekannt ist. Weggelassen: siehe Anleitung.
max_walk_to_destinationNoWie `max_walk_from_origin`, von der letzten Haltestelle zum Ziel.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / description
      Previous value: -"Unified connection request. For stops, provide origin_id and destination_id.\nFor arbitrary locations (e.g. addresses, POIs), provide coordinates — and as\nthe one retry worth making when resolved ids find nothing: an id the routing\ngraph does not know answers empty rather than with an error.\n\n`Default` is derived so a caller in a test can name the two or three fields\nits case is about; the request grows by optional fields often enough that\nspelling out two dozen `None`s at every call site is its own source of noise."New value: +"Unified connection request. For stops, provide origin_id and destination_id.\nFor arbitrary locations (e.g. addresses, POIs), provide coordinates — and as\nthe one retry worth making when a resolved id is refused: an id the timetable\ndoes not know is refused, not answered with no connection.\n\n`Default` is derived so a caller in a test can name the two or three fields\nits case is about; the request grows by optional fields often enough that\nspelling out two dozen `None`s at every call site is its own source of noise."
    • removedInput schema / properties / max_walk_from_origin / maximum
      Removed value: -5000
    • removedInput schema / properties / max_walk_to_destination / maximum
      Removed value: -5000
    • changedInput schema / properties / origin_lat / description
      Previous value: -"Origin latitude, WGS-84 decimal degrees — the fallback when no id is at\nhand, and the one retry worth making when resolved ids find nothing."New value: +"Origin latitude, WGS-84 decimal degrees — the fallback when no id is at\nhand, and the one retry worth making when a resolved id is refused."
  2. Changed2 schema fields changed
    • changedInput schema / properties / max_transfers / description
      Previous value: -"Upper bound on interchanges: `0` = direct, up to `3`. Omit unless the user\nconstrains transfers: the backend then derives the search depth from the\ntrip's air-line distance and escalates it when the first attempt finds\nnothing, so omitting never loses a connection."New value: +"Upper bound on interchanges: `0` = direct, up to `3`; another number is an\nargument error. Omit unless the user constrains transfers: the backend then\nderives the search depth from the trip's air-line distance and escalates it\nwhen the first attempt finds nothing, so omitting never loses a connection."
    • changedInput schema / properties / max_walk_minutes / description
      Previous value: -"Cap on the summed walking TIME in minutes: every journey of the answer\nkeeps to it."New value: +"Cap on the summed walking TIME in minutes, at least 1: every journey of the\nanswer keeps to it."
  3. Changed3 schema fields changed
    • addedInput schema / properties / time / default
      Added value: +null
    • changedInput schema / properties / time / description
      Previous value: -"ISO 8601 timestamp (e.g. `\"2026-06-15T08:30:00Z\"`). Omit to plan from now.\nResolve a spoken time with the time tool rather than computing one."New value: +"ISO 8601; without an offset local time in Berlin (`\"2026-11-06T08:30\"`). Omit to plan from\nnow. Resolve a spoken time with the time tool rather than computing one."
    • removedInput schema / properties / time / format
      Removed value: -"date-time"
  4. Changed9 schema fields changed
    • changedInput schema / properties / max_walk_from_origin / description
      Previous value: -"Höchstens so weit zu Fuß vom Start zur ersten Haltestelle, Meter über die Straße:\n500, 1000, 2000 oder 5000 — anderes ist ein Argument-Fehler."New value: +"Höchstens so weit zu Fuß vom Start zur ersten Haltestelle, Meter über die Straße: ganze\nMeter von 1 bis 5000; darüber gilt 5000, und `not_considered` sagt es."
    • removedInput schema / properties / max_walk_from_origin / enum
      Removed value: -[
      -  500,
      -  1000,
      -  2000,
      -  5000,
      -  null
      -]
    • addedInput schema / properties / max_walk_from_origin / examples
      Added value: +[
      +  500,
      +  1000,
      +  2000,
      +  5000
      +]
    • addedInput schema / properties / max_walk_from_origin / maximum
      Added value: +5000
    • addedInput schema / properties / max_walk_from_origin / minimum
      Added value: +1
    • removedInput schema / properties / max_walk_to_destination / enum
      Removed value: -[
      -  500,
      -  1000,
      -  2000,
      -  5000,
      -  null
      -]
    • addedInput schema / properties / max_walk_to_destination / examples
      Added value: +[
      +  500,
      +  1000,
      +  2000,
      +  5000
      +]
    • addedInput schema / properties / max_walk_to_destination / maximum
      Added value: +5000
    • addedInput schema / properties / max_walk_to_destination / minimum
      Added value: +1
  5. Changed2 schema fields changed
    • changedInput schema / properties / accessibility_profile / description
      Previous value: -"Mobility profile by name: `\"Standard\"` (default), `\"WheelchairRobust\"`,\n`\"WalkerComfort\"` or `\"IndividualComfort\"`. Each bundles its accessibility\nconstraints and walk speed; another name is an argument error. Where the\nwheelchair profiles find no stated step-free ride, `accessibility_routing`\nsays what the journeys beside it are. What each profile constrains is in the\nusage guide."New value: +"Mobility profile by name: `\"Standard\"` (default), `\"WheelchairRobust\"`,\n`\"WalkerComfort\"`, `\"PramComfort\"`, `\"VisuallyImpaired\"` or `\"IndividualComfort\"`.\nEach bundles its accessibility constraints and walk speed; another name is an argument\nerror. Where the step-free three (wheelchair, walker, pram) find no stated step-free\nride, `accessibility_routing` says what the journeys beside it are; these three and\n`VisuallyImpaired` note on a walk what the map knows (`additionalInfos.walkNotes`).\nWhat each profile constrains is in the usage guide."
    • changedInput schema / properties / accessibility_unknown / description
      Previous value: -"Nur mit `WheelchairRobust`/`WalkerComfort`: `refuse` nimmt nur als stufenfrei\nAusgewiesenes, `admit` auch, worüber nichts bekannt ist. Weggelassen: siehe Anleitung."New value: +"Nur mit `WheelchairRobust`/`WalkerComfort`/`PramComfort`: `refuse` nimmt nur als\nstufenfrei Ausgewiesenes, `admit` auch, worüber nichts bekannt ist. Weggelassen: siehe Anleitung."
  6. Changed1 schema field changed
    • addedInput schema / properties / stay_minutes
      Added value: +{
      +  "description": "Aufenthalt am Ziel, 0–1440 Minuten: ein Leihfahrzeug mit fester Station fährt damit hin\nund zurück; ohne ihn keins.",
      +  "format": "int64",
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
  7. Changed2 schema fields changed
    • addedInput schema / properties / change_reliability
      Added value: +{
      +  "description": "`true` nur, wenn der Nutzer nach der Verlässlichkeit der Umstiege fragt: dann sagen `change`\nund `reliability`, wie oft die Umstiege klappten. Weggelassen: nichts davon, außer mit\n`max_miss_risk`.",
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / max_miss_risk / description
      Previous value: -"Ab welchem Risiko, einen Umstieg zu verpassen, eine verlässlichere Alternative daneben steht:\nein Anteil von 0 bis 1 (`0.1` = 10 %). Weggelassen: nur die Chance jedes Umstiegs."New value: +"Ab welchem Risiko, einen Umstieg zu verpassen, eine verlässlichere Alternative daneben steht:\nein Anteil von 0 bis 1 (`0.1` = 10 %), auch ohne `change_reliability`. Weggelassen: keine\nAlternative."
  8. Changed1 schema field changed
    • addedInput schema / properties / max_miss_risk
      Added value: +{
      +  "description": "Ab welchem Risiko, einen Umstieg zu verpassen, eine verlässlichere Alternative daneben steht:\nein Anteil von 0 bis 1 (`0.1` = 10 %). Weggelassen: nur die Chance jedes Umstiegs.",
      +  "format": "double",
      +  "type": [
      +    "number",
      +    "null"
      +  ]
      +}
  9. Changed2 schema fields changed
    • changedInput schema / properties / modes / description
      Previous value: -"Transport-mode restriction, not a preference: nothing outside the list is\nplanned. The footpath always stays allowed — the way to, from and between\nstops goes on foot — while `[\"foot\"]` on its own plans no ride at all.\nEntries: `\"bike\"`, `\"bike_rental\"`, `\"foot\"`, `\"car\"`, `\"taxi\"`, `\"scooter\"`,\n`\"transit\"`, `\"bus\"`, `\"tram\"`, `\"rail\"`, `\"subway\"`, `\"ferry\"`; several\ncombine. An entry outside that list is an argument error, not a dropped\nfilter. Omitted or empty = all standard transit modes, the ferry\nincluded. Set only when the user insists on a mode; the guide has the\nvocabulary and the traps."New value: +"Transport-mode restriction, not a preference: nothing outside the list is\nplanned. The footpath always stays allowed — the way to, from and between\nstops goes on foot — while `[\"foot\"]` on its own plans no ride at all.\nEntries: `\"bike\"`, `\"bike_rental\"`, `\"foot\"`, `\"car\"`, `\"taxi\"`, `\"scooter\"`,\n`\"transit\"`, `\"bus\"`, `\"tram\"`, `\"rail\"`, `\"subway\"`, `\"ferry\"`, `\"air\"`\n(flights); several combine. An entry outside that list is an argument\nerror, not a dropped filter. Omitted or empty = all standard transit\nmodes, the ferry included, and a flight where one arrives sooner;\n`\"transit\"` = the same without flights. Set only when the user insists on\na mode; the guide has the vocabulary and the traps."
    • changedInput schema / properties / submodes_allow / description
      Previous value: -"Fine submode whitelist — finer than `modes`, which only separates\nbus/tram/rail/subway. Entries: `\"sbahn\"`, `\"regionalbahn\"`, `\"ice\"`,\n`\"ic\"`, `\"ir\"`, `\"nj\"`, `\"fernverkehr\"`, `\"stadtbahn\"`, `\"ubahn\"`,\n`\"bus\"`, `\"regionalbus\"`, `\"stadtbus\"`. A journey is kept only if every\ntransit leg matches one."New value: +"Fine submode whitelist — finer than `modes`, which only separates\nbus/tram/rail/subway. Entries: `\"sbahn\"`, `\"regionalbahn\"`, `\"ice\"`,\n`\"ic\"`, `\"ir\"`, `\"nj\"`, `\"fernverkehr\"`, `\"stadtbahn\"`, `\"ubahn\"`,\n`\"bus\"`, `\"regionalbus\"`, `\"stadtbus\"`, `\"flug\"` (flights). A journey is\nkept only if every transit leg matches one."
  10. Changed1 schema field changed
    • addedInput schema / properties / lang
      Added value: +{
      +  "description": "Die Sprache der Namen: `'de'` (Vorgabe), `'it'`, `'fr'`, auch mit Region (`'de-CH'`).",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  11. Changed1 schema field changed
    • changedInput schema / properties / origin_id / description
      Previous value: -"Origin id: the resolver's `main` id as handed out — for a stop a DHID (`de:NNNNN:NNN`,\n`at:…`, `ch:…`) or a station id (`Parentch:1:sloid:3000`), else the address or POI id.\nResolve the place first — a name here is an argument error."New value: +"Origin id: the resolver's `main` id as handed out — for a stop a DHID (`de:NNNNN:NNN`,\n`at:…`, `ch:…`, `it:…`) or a station id (`Parentch:1:sloid:3000`), else the address or POI id.\nResolve the place first — a name here is an argument error."
  12. Changed1 schema field changed
    • changedInput schema / properties / origin_id / description
      Previous value: -"Origin id. A DHID (`de:NNNNN:NNN`; in Austria and Switzerland `at:…`/`ch:…`)\nfor a stop, otherwise the resolver's `main` id of the address or POI. Resolve the place first — a name here is\nan argument error."New value: +"Origin id: the resolver's `main` id as handed out — for a stop a DHID (`de:NNNNN:NNN`,\n`at:…`, `ch:…`) or a station id (`Parentch:1:sloid:3000`), else the address or POI id.\nResolve the place first — a name here is an argument error."
  13. Changed4 schema fields changed
    • addedInput schema / properties / max_walk_from_origin
      Added value: +{
      +  "default": null,
      +  "description": "Höchstens so weit zu Fuß vom Start zur ersten Haltestelle, Meter über die Straße:\n500, 1000, 2000 oder 5000 — anderes ist ein Argument-Fehler.",
      +  "enum": [
      +    500,
      +    1000,
      +    2000,
      +    5000,
      +    null
      +  ],
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / max_walk_minutes / description
      Previous value: -"Cap on the summed walking TIME in minutes. A post-filter drops journeys\nabove it; if that leaves nothing, the backend searches once more avoiding\nfootpaths before the answer is empty."New value: +"Cap on the summed walking TIME in minutes: every journey of the answer\nkeeps to it."
    • addedInput schema / properties / max_walk_to_destination
      Added value: +{
      +  "default": null,
      +  "description": "Wie `max_walk_from_origin`, von der letzten Haltestelle zum Ziel.",
      +  "enum": [
      +    500,
      +    1000,
      +    2000,
      +    5000,
      +    null
      +  ],
      +  "type": [
      +    "integer",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / origin_id / description
      Previous value: -"Origin id. A DHID (`de:NNNNN:NNN`) for a stop, otherwise the resolver's\n`main` id of the address or POI. Resolve the place first — a name here is\nan argument error."New value: +"Origin id. A DHID (`de:NNNNN:NNN`; in Austria and Switzerland `at:…`/`ch:…`)\nfor a stop, otherwise the resolver's `main` id of the address or POI. Resolve the place first — a name here is\nan argument error."
  14. Changed1 schema field changed
    • changedInput schema / properties / origin_type / description
      Previous value: -"What `origin_id` is: `\"stop\"` (default), `\"address\"` or `\"poi\"`. A stop id\nis auto-prefixed `GTFS.de:`; the other two are forwarded verbatim so the\nbackend resolves the real name."New value: +"What `origin_id` is: `\"stop\"` (default), `\"address\"` or `\"poi\"`. The backend\nresolves an address or a POI to its real name from the id."
  15. Changed1 schema field changed
    • addedInput schema / properties / taxi_pickup
      Added value: +{
      +  "description": "Wo das Taxi die Fahrten trifft: `door` (Default, am Halt) oder `rank` (am Taxistand).",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  16. Changed10 schema fields changed
    • addedInput schema / $defs
      Added value: +{
      +  "BikeCarriageArgument": {
      +    "anyOf": [
      +      {
      +        "type": "boolean"
      +      },
      +      {
      +        "type": "string"
      +      }
      +    ]
      +  },
      +  "ViaRequest": {
      +    "description": "Ein Zwischenhalt.",
      +    "properties": {
      +      "id": {
      +        "description": "Id wie `origin_id`.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "kind": {
      +        "description": "`through` (Default: durchfahren genügt) oder `stopover` (dort umsteigen).",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "lat": {
      +        "description": "Breite eines Orts ohne Id, mit `lon`.",
      +        "format": "double",
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "lon": {
      +        "description": "Länge, mit `lat`.",
      +        "format": "double",
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "stay_minutes": {
      +        "description": "Mindest-Aufenthalt, 0–1440 Minuten; macht den Halt zum Umstieg.",
      +        "format": "int64",
      +        "type": [
      +          "integer",
      +          "null"
      +        ]
      +      },
      +      "type": {
      +        "description": "Wie `origin_type`.",
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": "object"
      +  }
      +}
    • addedInput schema / properties / access_modes
      Added value: +{
      +  "description": "Weg zur ersten Haltestelle: Einträge `fahrzeug[:own|sharing][:only|prefer]`, Fahrzeug\n`walk`, `bike`, `scooter`, `car`, `taxi`; `own`/`sharing` eigenes/geliehenes (sonst\ngleich wessen); `only` nur damit, `prefer` (Default) neben dem Fußweg.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / accessibility_profile / description
      Previous value: -"Mobility profile by name: `\"Standard\"` (default), `\"WheelchairRobust\"`,\n`\"WalkerComfort\"` or `\"IndividualComfort\"`. Each bundles its accessibility\nconstraints and walk speed; another name is an argument error. The two\nwheelchair profiles find no ride at all today — the answer then carries\n`accessibility_routing` with `status: no_data` beside ordinary connections,\nwhich are to be reported as ordinary ones. What each profile constrains is\nin the usage guide."New value: +"Mobility profile by name: `\"Standard\"` (default), `\"WheelchairRobust\"`,\n`\"WalkerComfort\"` or `\"IndividualComfort\"`. Each bundles its accessibility\nconstraints and walk speed; another name is an argument error. Where the\nwheelchair profiles find no stated step-free ride, `accessibility_routing`\nsays what the journeys beside it are. What each profile constrains is in the\nusage guide."
    • addedInput schema / properties / accessibility_unknown
      Added value: +{
      +  "description": "Nur mit `WheelchairRobust`/`WalkerComfort`: `refuse` nimmt nur als stufenfrei\nAusgewiesenes, `admit` auch, worüber nichts bekannt ist. Weggelassen: siehe Anleitung.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / bike_carriage
      Added value: +{
      +  "anyOf": [
      +    {
      +      "$ref": "#/$defs/BikeCarriageArgument"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Das Rad fährt auf jeder Fahrt mit: `true` nur auf Fahrten, die es bekanntlich\nmitnehmen, `'allow_unknown'` auch ohne Angabe."
      +}
    • addedInput schema / properties / cancelled
      Added value: +{
      +  "description": "`exclude` (Default), `include` (dazu `broken_journeys` mit Grund) oder `mark` (dazu\njeder Halt beurteilt und wo neu zu suchen ist).",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / egress_modes
      Added value: +{
      +  "description": "Wie `access_modes`, für den Weg von der letzten Haltestelle.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / no_change_at
      Added value: +{
      +  "description": "Halt-Ids wie `origin_id`, an denen keine Verbindung umsteigt.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / not_via
      Added value: +{
      +  "description": "Halt-Ids wie `origin_id`, die keine Verbindung berührt.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / vias
      Added value: +{
      +  "description": "Zwischenhalte in Reiserichtung, höchstens 4, statt `via_id`/`via_lat`/`via_lon`:\nje `id`+`type` (wie ein Endpunkt) oder `lat`+`lon`, dazu `kind`, `stay_minutes`.",
      +  "items": {
      +    "$ref": "#/$defs/ViaRequest"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
  17. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly=true, destructive=false, openWorld=true), and the description adds real behavioural detail beyond them: `render_payload` is dropped, the answer text is identical to `connections` but the raw data beside it carries only the fields the view draws, in local time, with the map progression in `_meta`. It does not spell out concretely how the 'script' delivery surfaces to the caller, which keeps it off a 5.

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

Conciseness4/5

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

Bold headers front-load the key distinction and the routing rule before the parameter detail, which is the right order. The repeated 'wie dort' / 'wie `connections`' framing is slightly redundant but functionally useful for keeping the delta from the sibling explicit.

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 48-parameter planning tool with no output schema, the description covers what is actually needed: how it differs from `connections`, the mandatory endpoints, the opt-in flags, and the shape of the response (text plus view-specific raw data in `_meta`). The remaining parameter depth is legitimately delegated to the schema and the 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 description coverage is 100%, so the baseline is 3, but the description adds important meaning the schema does not declare: the schema lists zero required parameters while the description insists BOTH endpoints (`origin_id` AND `destination_id`, or the four coordinate fields) are mandatory. It also flags the opt-in nature of `change_reliability`, `max_miss_risk` and car sharing via `stay_minutes`.

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 first clause states exactly what it is: the same connection view as `show_connections`, but delivered slim, with the map widget loading the view as a script instead of it being carried inline. It also names the sibling it is not, so an agent can distinguish the two 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 Guidelines5/5

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

Explicit routing rule: 'Nimm dies nur, wenn ausdrücklich nach der schlanken Auslieferung gefragt wird — sonst `show_connections`.' That gives the when-to-use, the when-not, and the named alternative in a single sentence, and points to `get_usage_guide` with `tool='connections'` for the rest.

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