STPT MCP

Get STPT stop details

get_stop

Read-onlyIdempotent

Retrieve coordinates, serving lines, directions, terminals, and neighboring stops for a numeric STPT stop ID to plan and navigate public transport in Timișoara.

Instructions

Get coordinates, serving lines, directions, terminals, and neighboring stops for a numeric STPT stop ID.

Input Schema

Name	Required	Description	Default
`stop_id`	Yes	Numeric STPT stop ID.

Output Schema

Name	Required	Description
`stop`	No
`error`	No	Structured failure, if any.
`status`	Yes	Overall result status.
`provenance`	No	Source and freshness metadata.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedv0.3.7Oct 23, 2026

addedOutput schema / $defs / Freshness

Added value: +{
+  "enum": [
+    "fresh",
+    "stale",
+    "unverified"
+  ],
+  "title": "Freshness",
+  "type": "string"
+}

changedOutput schema / $defs / Provenance / properties / data_age_seconds / description

Previous value: -"Age of the source/cache entry when returned."New value: +"Age of the upstream observation when returned, in seconds. Null when the age cannot be measured."

addedOutput schema / $defs / Provenance / properties / freshness

Added value: +{
+  "$ref": "#/$defs/Freshness",
+  "default": "unverified",
+  "description": "fresh: an upstream observation time was checked against this server's clock and is within tolerance. stale: the check failed (old, clock-skewed, or frozen data) or a cache entry past its TTL is served. unverified: the data carries no upstream clock reference (schedules, the network snapshot, alerts), so it cannot be confirmed as current."
+}

changedOutput schema / $defs / Provenance / properties / is_stale / description

Previous value: -"True when the stale cache policy supplied the data."New value: +"True when stale data is being returned, whether from cache or upstream."

changedOutput schema / $defs / Provenance / properties / observed_at / description

Previous value: -"Upstream observation timestamp. Live arrivals expose no timestamp, so this is the fetch time; schedules describe future service and leave it null; vehicles use their upstream timestamp."New value: +"Upstream observation timestamp in UTC. Live arrivals derive it from the feed's own display times and remaining minutes; it is null when the feed carries no clock reference or is rejected as stale. Schedules describe future service and leave it null; vehicles use their upstream timestamp."

First observedv0.2.0Oct 21, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds useful scope information by naming the returned facets (including neighboring stops, a non-obvious extra), but says nothing about behavior on invalid IDs or how fresh/complete the data is.

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?

One tightly packed sentence: the action leads, the returned fields are enumerated, and the input constraint trails. Zero filler.

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 an output schema covering return shape and annotations covering safety, the description is nearly complete. The only residual gap is how an agent should obtain a valid stop ID (e.g., via search_stops), which would round it out.

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 parameter is documented as 'Numeric STPT stop ID.' The description restates the same constraint without adding format, range, or sourcing guidance, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Get ... stop details') and enumerates exactly what is returned: coordinates, serving lines, directions, terminals, and neighboring stops, keyed by a numeric STPT stop ID. This distinguishes it well from siblings like get_arrivals, though it does not explicitly contrast it with search_stops.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is only implied by the 'numeric STPT stop ID' phrasing — an agent can infer it is the lookup-by-ID tool versus search_stops' query-based discovery, but no when/when-not or alternative is named. No prerequisites or failure conditions for an unknown ID are mentioned.

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

Deploy Server