Transit Land

Search Stops

search_stops

Read-onlyIdempotent

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

Example tool call

This call uses example arguments supplied in the tool’s input schema.

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

Input 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

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 1, 2026
- changedOutput schema / properties / stops / items / properties / stop_code / type
```
Previous value: -"string"New value: +[
+  "string",
+  "null"
+]
```

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

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 by structured data. The description adds no further behavioral context such as result ordering, coverage limits, or how the four search modes interact, so it does only modest work.

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?

Two short sentences with the core action front-loaded and no filler. It is efficient, though arguably terse to the point of omitting necessary detail rather than being optimally concise.

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

Completeness2/5

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

For a 7-parameter tool supporting geospatial, free-text, stop_id, and route-type search modes, the description covers only the geospatial case. With an output schema present it need not explain returns, but the missing mode guidance leaves the definition materially incomplete.

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 coverage is 57%, so roughly half the parameters are undocumented. The description adds one useful semantic grouping (lat+lon+radius_m as 'stops near point') but leaves the query, stop_id, and served_by_route_type modes unexplained, so it does not compensate for the coverage gap.

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 ('search stops/stations') that clearly distinguishes it from siblings like search_routes and search_agencies. However, it does not frame itself against those siblings or explain the scope of the search.

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?

Gives one explicit usage pattern ('Use lat+lon+radius_m for stops near point'), which implies the geospatial mode, but says nothing about the other supported modes (query text, stop_id, served_by_route_type) or when to prefer those.

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

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.