Transit Land

Search Stops

search_stops

Read-onlyIdempotent

Search stops/stations. Use lat+lon+radius_m for "stops near point".

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No
`lon`	No
`limit`	No
`query`	No	Free-text search by stop/station name
`stop_id`	No	GTFS stop_id
`radius_m`	No	Default 100
`served_by_route_type`	No	Filter to stops served by this route_type

Output Schema

TableJSON Schema

Name	Required	Description	Default
`meta`	No
`stops`	No	List of matching stops

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJul 29, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "name": "Market Street"
-  },
-  {
-    "lat": 40.7128,
-    "limit": 15,
-    "lon": -74.006,
-    "radius_m": 500
-  }
-]New value: +[
+  {},
+  {
+    "lat": 40.7128,
+    "limit": 15,
+    "lon": -74.006,
+    "radius_m": 500
+  }
+]

Changed2 schema fields changedJun 26, 2026

removedInput schema / properties / name

Removed value: -{
-  "type": "string"
-}

addedInput schema / properties / query

Added value: +{
+  "description": "Free-text search by stop/station name",
+  "type": "string"
+}

Changed19 schema fields changedJun 2, 2026

addedOutput schema / properties / meta

Added value: +{
+  "properties": {
+    "after": {
+      "type": "number"
+    },
+    "next": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / stops / items / properties / feed_version

Added value: +{
+  "properties": {
+    "feed": {
+      "properties": {
+        "id": {
+          "type": "number"
+        },
+        "onestop_id": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "fetched_at": {
+      "type": "string"
+    },
+    "id": {
+      "type": "number"
+    },
+    "sha1": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / stops / items / properties / geometry / properties

Added value: +{
+  "coordinates": {
+    "items": {
+      "type": "number"
+    },
+    "type": "array"
+  },
+  "type": {
+    "type": "string"
+  }
+}

changedOutput schema / properties / stops / items / properties / id / type
```
Previous value: -"string"New value: +"number"
```
addedOutput schema / properties / stops / items / properties / level
```
Added value: +{
+  "type": "null"
+}
```

removedOutput schema / properties / stops / items / properties / name

Removed value: -{
-  "description": "Stop name",
-  "type": "string"
-}

addedOutput schema / properties / stops / items / properties / onestop_id
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / stops / items / properties / parent
```
Added value: +{
+  "type": "null"
+}
```

addedOutput schema / properties / stops / items / properties / place

Added value: +{
+  "properties": {
+    "adm0_iso": {
+      "type": "string"
+    },
+    "adm0_name": {
+      "type": "string"
+    },
+    "adm1_iso": {
+      "type": "string"
+    },
+    "adm1_name": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

changedOutput schema / properties / stops / items / properties / platform_code / type
```
Previous value: -"string"New value: +"null"
```

removedOutput schema / properties / stops / items / properties / served_by_route_types

Removed value: -{
-  "description": "GTFS route_type codes serving this stop",
-  "items": {
-    "type": "number"
-  },
-  "type": "array"
-}

addedOutput schema / properties / stops / items / properties / stop_code
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / stops / items / properties / stop_desc
```
Added value: +{
+  "type": "null"
+}
```
addedOutput schema / properties / stops / items / properties / stop_name
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / stops / items / properties / stop_timezone
```
Added value: +{
+  "type": "null"
+}
```
addedOutput schema / properties / stops / items / properties / stop_url
```
Added value: +{
+  "type": "null"
+}
```
addedOutput schema / properties / stops / items / properties / tts_stop_name
```
Added value: +{
+  "type": "null"
+}
```
addedOutput schema / properties / stops / items / properties / wheelchair_boarding
```
Added value: +{
+  "type": "number"
+}
```
addedOutput schema / properties / stops / items / properties / zone_id
```
Added value: +{
+  "type": "null"
+}
```

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name": "Market Street"
+  },
+  {
+    "lat": 40.7128,
+    "limit": 15,
+    "lon": -74.006,
+    "radius_m": 500
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Search results for transit stops/stations",
+  "properties": {
+    "stops": {
+      "description": "List of matching stops",
+      "items": {
+        "properties": {
+          "geometry": {
+            "description": "GeoJSON point geometry with lat/lon",
+            "type": "object"
+          },
+          "id": {
+            "description": "Transitland onestop_id",
+            "type": "string"
+          },
+          "location_type": {
+            "description": "0=stop, 1=station, etc",
+            "type": "number"
+          },
+          "name": {
+            "description": "Stop name",
+            "type": "string"
+          },
+          "platform_code": {
+            "description": "Platform identifier",
+            "type": "string"
+          },
+          "served_by_route_types": {
+            "description": "GTFS route_type codes serving this stop",
+            "items": {
+              "type": "number"
+            },
+            "type": "array"
+          },
+          "stop_id": {
+            "description": "GTFS stop_id",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds no new behavioral context (e.g., pagination, limits, or data freshness). It does not contradict annotations.

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?

Two sentences, front-loaded with purpose and a concrete example. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema, return values are covered. However, the 7-parameter tool has no required parameters and the description only addresses one use case. Missing guidance on other parameters and cross-use with sibling tools.

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 57%, and the description adds context for lat+lon+radius_m ('stops near point'). However, it does not explain other parameters like stop_id, query, or served_by_route_type beyond what the schema already provides.

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?

The description clearly states 'Search stops/stations' and provides a specific use case ('stops near point' with lat+lon+radius_m). It differentiates itself from siblings like search_routes or search_agencies by focusing on stops, though not explicitly.

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 gives one explicit usage scenario (stops near point) but does not compare with alternatives or specify when not to use. Usage guidance is implied rather than explicit.

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

All Transit Land tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.