Skip to main content
Glama
Sign In
gtfs-scorecard

gtfs-scorecard

by ChelseaKR
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

search_agencies

Search tracked GTFS transit agencies by name, ID, country, subdivision, state, or letter grade; return location, grade, score, expiry, and readiness data.

Instructions

Search tracked transit agencies by name, id, ISO country, ISO subdivision or subdivision name, legacy state, or letter grade. Returns portable location, grade, score, expiry, and applicable readiness fields.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
gradeNoLetter grade A-F
limitNoMax results (default 20)
queryNoName fragment or exact agency id
stateNoLegacy state/province-name filter; prefer subdivision
countryNoISO 3166-1 alpha-2 country code, e.g. CA
subdivisionNoISO 3166-2 code or subdivision name, e.g. CA-ON or Ontario

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It partially does so by disclosing the returned fields (portable location, grade, score, expiry, readiness), which is valuable given there is no output schema. But it says nothing about read-only nature, ordering, pagination beyond the schema's limit default, or auth requirements.

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, zero filler, and the search scope is front-loaded before the return-value sentence. Every clause (filter dimensions, returned fields) carries distinct information.

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?

Given no output schema, the description usefully enumerates the return payload, which is the main completeness risk. It falls slightly short on pagination/ordering and filter-combination behavior for a six-parameter search tool, but nothing critical for a correct call is missing.

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 the schema already documents all six parameters including the 'prefer subdivision' hint. The description groups and names the same dimensions but adds no syntax, format, or interaction semantics (e.g., AND vs OR across filters) beyond what the schema provides; baseline 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?

States a specific verb (Search) and resource (tracked transit agencies), then enumerates the searchable dimensions (name, id, ISO country, subdivision, legacy state, grade). This clearly separates it from stats/aggregation siblings such as national_stats, get_rollup, and get_scorecard, which return computed values rather than agency records.

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 implied by the enumeration of filter dimensions, so an agent can infer this is the lookup tool for individual agencies. However, there is no explicit when-to-use versus alternatives (e.g., coverage_for or get_scorecard for aggregate views) and no guidance on combining filters or when results are exhaustive.

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

Deploy Server

Other Tools