Lviv Public Transport

Get Vehicle Info

get_vehicle_info

Read-onlyIdempotent

Returns details for one vehicle by ID: position, route, destination, license plate, and its upcoming stops with names and estimated arrival times. Use when the user wants to follow a particular vehicle, e.g. "where does this tram go next?" or "when will it reach X?". Vehicle IDs come from get_route_realtime, get_nearby_vehicles, or get_stop_realtime results. Do NOT use this to get all vehicles on a route — use get_route_realtime instead.

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": {
      "vehicle_id": "<vehicle_id>"
    },
    "name": "get_vehicle_info"
  }
}

Input Schema

Name	Required	Description	Default
`vehicle_id`	Yes	Vehicle ID as returned by get_route_realtime, get_nearby_vehicles, or get_stop_realtime.

Output Schema

Name	Required	Description	Default
`data`	Yes
`view`	Yes
`ui_blocks`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 4, 2026
- removedOutput schema / properties / ui_blocks / items / properties / data / properties / center / additionalItems
```
Removed value: -false
```
- changedOutput schema / properties / ui_blocks / items / properties / data / properties / center / items
```
Previous value: -[
-  {
-    "type": [
-      "number",
-      "null"
-    ]
-  },
-  {
-    "type": [
-      "number",
-      "null"
-    ]
-  }
-]New value: +false
```
- addedOutput schema / properties / ui_blocks / items / properties / data / properties / center / prefixItems
```
Added value: +[
+  {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  {
+    "type": [
+      "number",
+      "null"
+    ]
+  }
+]
```
Changed10 schema fields changedNov 2, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- removedOutput schema / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / data / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / data / properties / direction / anyOf
```
Removed value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": -9007199254740991,
-    "type": "integer"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / direction / type
```
Added value: +[
+  "integer",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / upcoming_stops / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / ui_blocks / items / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / ui_blocks / items / properties / data / additionalProperties
```
Removed value: -false
```
- removedOutput schema / properties / ui_blocks / items / properties / data / properties / layers / additionalProperties
```
Removed value: -false
```

Changed9 schema fields changedSep 23, 2026

addedOutput schema / properties / data / properties / destination

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

removedOutput schema / properties / data / properties / upcoming_stops / items / properties / code

Removed value: -{
-  "maximum": 9007199254740991,
-  "minimum": -9007199254740991,
-  "type": "integer"
-}

addedOutput schema / properties / data / properties / upcoming_stops / items / properties / id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / data / properties / upcoming_stops / items / properties / name
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / properties / data / properties / upcoming_stops / items / required

Previous value: -[
-  "code",
-  "arrival",
-  "departure"
-]New value: +[
+  "id",
+  "name",
+  "arrival",
+  "departure"
+]

changedOutput schema / properties / data / required

Previous value: -[
-  "vehicle_id",
-  "route",
-  "license_plate",
-  "lat",
-  "lng",
-  "bearing",
-  "direction",
-  "upcoming_stops",
-  "updated_at"
-]New value: +[
+  "vehicle_id",
+  "route",
+  "license_plate",
+  "lat",
+  "lng",
+  "bearing",
+  "direction",
+  "destination",
+  "upcoming_stops",
+  "updated_at"
+]

addedOutput schema / properties / ui_blocks / items / properties / data / properties / layers

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "polylines": {
+      "type": "string"
+    },
+    "stops": {
+      "type": "string"
+    },
+    "vehicles": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / ui_blocks / items / properties / data / properties / vehicles

Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "bearing": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "eta_minutes": {
-        "anyOf": [
-          {
-            "maximum": 9007199254740991,
-            "minimum": -9007199254740991,
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "eta_status": {
-        "enum": [
-          "assigned",
-          "unassigned"
-        ],
-        "type": "string"
-      },
-      "id": {
-        "type": "string"
-      },
-      "lat": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "lng": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "next_stop_id": {
-        "type": [
-          "string",
-          "null"
-        ]
-      },
-      "route": {
-        "type": [
-          "string",
-          "null"
-        ]
-      }
-    },
-    "required": [
-      "id",
-      "route",
-      "lat",
-      "lng",
-      "bearing",
-      "next_stop_id",
-      "eta_minutes",
-      "eta_status"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}

changedOutput schema / properties / ui_blocks / items / properties / data / required

Previous value: -[
-  "center",
-  "zoom",
-  "vehicles"
-]New value: +[
+  "center",
+  "zoom",
+  "layers"
+]

Changed28 schema fields changedSep 6, 2026
- removedOutput schema / properties / data / properties / bearing / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / bearing / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / lat / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / lat / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / license_plate / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / license_plate / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / lng / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / lng / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / route / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / route / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / upcoming_stops / items / properties / arrival / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / upcoming_stops / items / properties / arrival / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / data / properties / upcoming_stops / items / properties / departure / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / data / properties / upcoming_stops / items / properties / departure / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- addedOutput schema / properties / ui_blocks / items / properties / data / properties / center / additionalItems
```
Added value: +false
```
- changedOutput schema / properties / ui_blocks / items / properties / data / properties / center / items
```
Previous value: -[
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  }
-]New value: +[
+  {
+    "type": [
+      "number",
+      "null"
+    ]
+  },
+  {
+    "type": [
+      "number",
+      "null"
+    ]
+  }
+]
```
- addedOutput schema / properties / ui_blocks / items / properties / data / properties / center / maxItems
```
Added value: +2
```
- addedOutput schema / properties / ui_blocks / items / properties / data / properties / center / minItems
```
Added value: +2
```
- removedOutput schema / properties / ui_blocks / items / properties / data / properties / vehicles / items / properties / bearing / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / ui_blocks / items / properties / data / properties / vehicles / items / properties / bearing / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / ui_blocks / items / properties / data / properties / vehicles / items / properties / lat / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / ui_blocks / items / properties / data / properties / vehicles / items / properties / lat / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / ui_blocks / items / properties / data / properties / vehicles / items / properties / lng / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / ui_blocks / items / properties / data / properties / vehicles / items / properties / lng / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / ui_blocks / items / properties / data / properties / vehicles / items / properties / next_stop_id / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / ui_blocks / items / properties / data / properties / vehicles / items / properties / next_stop_id / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / ui_blocks / items / properties / data / properties / vehicles / items / properties / route / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / ui_blocks / items / properties / data / properties / vehicles / items / properties / route / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedMay 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered; the description still adds behavioral value by stating the single-vehicle scope and that results include upcoming stops with estimated arrival times. It omits edge behavior such as what happens with an unknown or stale vehicle ID, which is the main remaining gap given the response schema already documents the shape.

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?

Three tightly packed sentences: capability and payload first, usage and provenance second, anti-pattern third. No filler and the ordering is front-loaded for fast triage.

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?

One required parameter, full schema coverage, an output schema that carries the return shape, and rich annotations — the description supplies exactly the missing layer (when to use it, where IDs come from, which sibling to prefer) without redundant explanation.

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

Parameters3/5

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

Schema description coverage is 100% and the single vehicle_id parameter is already documented with its provenance, so the description's mention of ID sources largely restates the schema. There is no extra guidance on ID format, case sensitivity, or what to do if an ID is rejected, so baseline 3 applies.

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?

Specific verb+resource ('Returns details for one vehicle by ID') plus an enumeration of the payload (position, route, destination, license plate, upcoming stops with ETAs), and it explicitly distinguishes itself from get_route_realtime, which returns all vehicles on a route.

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?

Gives an explicit when-to-use with two natural-language user intents, states the prerequisite (where vehicle IDs come from — get_route_realtime, get_nearby_vehicles, get_stop_realtime), and adds an explicit 'do NOT use this... use get_route_realtime instead' exclusion that routes the agent to the right sibling.

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

All Lviv Public Transport tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.