Transit Land

Search Agencies

search_agencies

Read-onlyIdempotent

Search transit agencies/operators by name or geo. Operators are the entities running services.

Input Schema

TableJSON Schema

Name	Required	Description
`lat`	No	Latitude (with radius_m + lon)
`lon`	No	Longitude
`limit`	No	1-100 (default 20)
`query`	No	Free-text search by agency/operator name (e.g. "BART", "MTA")
`radius_m`	No	Search radius in meters (default 1000)
`agency_id`	No	GTFS agency_id

Output Schema

TableJSON Schema

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

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": "Bay Area Rapid Transit"
-  },
-  {
-    "lat": 37.7749,
-    "limit": 10,
-    "lon": -122.4194,
-    "radius_m": 5000
-  }
-]New value: +[
+  {},
+  {
+    "lat": 37.7749,
+    "limit": 10,
+    "lon": -122.4194,
+    "radius_m": 5000
+  }
+]

Changed2 schema fields changedJun 26, 2026

removedInput schema / properties / name

Removed value: -{
-  "description": "Free-text agency name filter",
-  "type": "string"
-}

addedInput schema / properties / query

Added value: +{
+  "description": "Free-text search by agency/operator name (e.g. \"BART\", \"MTA\")",
+  "type": "string"
+}

Changed20 schema fields changedJun 2, 2026

addedOutput schema / properties / agencies / items / properties / agency_email
```
Added value: +{
+  "type": "null"
+}
```
addedOutput schema / properties / agencies / items / properties / agency_fare_url
```
Added value: +{
+  "type": "null"
+}
```
addedOutput schema / properties / agencies / items / properties / agency_lang
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / agencies / items / properties / agency_name
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / agencies / items / properties / agency_phone
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / agencies / items / properties / agency_timezone
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / agencies / items / properties / agency_url
```
Added value: +{
+  "type": "string"
+}
```

removedOutput schema / properties / agencies / items / properties / email

Removed value: -{
-  "description": "Contact email",
-  "type": "string"
-}

addedOutput schema / properties / agencies / 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 / agencies / items / properties / geometry / properties

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

changedOutput schema / properties / agencies / items / properties / id / type
```
Previous value: -"string"New value: +"number"
```

removedOutput schema / properties / agencies / items / properties / language

Removed value: -{
-  "description": "ISO language code",
-  "type": "string"
-}

removedOutput schema / properties / agencies / items / properties / name

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

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

addedOutput schema / properties / agencies / items / properties / operator

Added value: +{
+  "properties": {
+    "feeds": {
+      "items": {
+        "properties": {
+          "id": {
+            "type": "number"
+          },
+          "name": {
+            "type": "null"
+          },
+          "onestop_id": {
+            "type": "string"
+          },
+          "spec": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "name": {
+      "type": "string"
+    },
+    "onestop_id": {
+      "type": "string"
+    },
+    "short_name": {
+      "type": [
+        "null",
+        "string"
+      ]
+    },
+    "tags": {
+      "type": "null"
+    }
+  },
+  "type": "object"
+}

removedOutput schema / properties / agencies / items / properties / phone

Removed value: -{
-  "description": "Contact phone number",
-  "type": "string"
-}

addedOutput schema / properties / agencies / items / properties / places

Added value: +{
+  "items": {
+    "properties": {
+      "adm0_name": {
+        "type": "string"
+      },
+      "adm1_name": {
+        "type": "string"
+      },
+      "city_name": {
+        "type": [
+          "string",
+          "null"
+        ]
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

removedOutput schema / properties / agencies / items / properties / timezone

Removed value: -{
-  "description": "IANA timezone",
-  "type": "string"
-}

removedOutput schema / properties / agencies / items / properties / url

Removed value: -{
-  "description": "Agency website URL",
-  "type": "string"
-}

addedOutput schema / properties / meta

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

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name": "Bay Area Rapid Transit"
+  },
+  {
+    "lat": 37.7749,
+    "limit": 10,
+    "lon": -122.4194,
+    "radius_m": 5000
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "Search results for transit agencies/operators",
+  "properties": {
+    "agencies": {
+      "description": "List of matching agencies",
+      "items": {
+        "properties": {
+          "agency_id": {
+            "description": "GTFS agency_id",
+            "type": "string"
+          },
+          "email": {
+            "description": "Contact email",
+            "type": "string"
+          },
+          "geometry": {
+            "description": "GeoJSON geometry",
+            "type": "object"
+          },
+          "id": {
+            "description": "Transitland onestop_id",
+            "type": "string"
+          },
+          "language": {
+            "description": "ISO language code",
+            "type": "string"
+          },
+          "name": {
+            "description": "Agency name",
+            "type": "string"
+          },
+          "phone": {
+            "description": "Contact phone number",
+            "type": "string"
+          },
+          "timezone": {
+            "description": "IANA timezone",
+            "type": "string"
+          },
+          "url": {
+            "description": "Agency website URL",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

First observedMay 13, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare the tool as read-only, non-destructive, and idempotent. The description adds minor context (e.g., 'operators are the entities running services'), but does not disclose additional behavioral traits like pagination, rate limits, or result ordering.

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 with no filler. The first sentence states the purpose and scope, the second clarifies what 'operators' are. Every word earns its place.

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?

Given the good annotations and output schema, the description is adequate but lacks usage guidelines to differentiate from siblings. It does not describe return value structure (though output schema covers that) or explain parameter interactions.

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

Parameters4/5

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

The input schema has 100% description coverage, so the description adds relatively little. However, it provides high-level grouping ('by name or geo') that helps agents understand the two main parameter modes (query vs. lat/lon/radius), which is not explicitly in the schema.

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?

The description clearly states the tool searches 'transit agencies/operators by name or geo' and clarifies that operators are entities running services. This distinguishes it from sibling search tools like 'search_routes' and '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 Guidelines2/5

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

The description does not provide any guidance on when to use this tool versus alternatives such as 'search_routes' or 'search_stops', nor does it mention prerequisites or limitations.

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.