STPT MCP

Search STPT stops

search_stops

Read-onlyIdempotent

Locate STPT stops by stop code, name fragment, or line number with diacritic-insensitive matching, returning up to 50 results.

Instructions

Search the bundled STPT network by stop ID, stop name, or line. Uses diacritic-insensitive matching. Returns up to 50 stops.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of stops to return.
`query`	Yes	Stop code, stop name fragment, or line number.

Output Schema

Name	Required	Description
`count`	Yes
`error`	No	Structured failure, if any.
`query`	Yes
`stops`	No
`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

A4/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and open-world. The description adds genuine behavioral detail beyond them: diacritic-insensitive matching and a hard result cap of 50, both of which affect how an agent should query and interpret results.

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 short sentences with no filler, and the core action and scope are front-loaded before the matching and result-count details.

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 present and full parameter documentation, the description covers what is needed to call the tool correctly. The only omission is how the tool relates to the sibling get_stop for exact-ID lookups.

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%, so both query and limit are already documented with examples and bounds. The description's mention of 'up to 50 stops' and the match types only restates schema-level facts, so the baseline of 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 (Search) plus resource (STPT stops) and explicit scope ('bundled STPT network'). It also names the three match keys, so an agent can immediately tell this apart from get_stop (single-stop lookup) and list_routes.

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?

The description implies usage through the set of searchable keys (stop ID, name, line), which lets an agent infer when to reach for it. However, it never explicitly says when to prefer it over the sibling get_stop, nor any exclusions or prerequisites.

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

Deploy Server