Skip to main content
Glama

List Feeds

list_feeds
Read-onlyIdempotent

List available GTFS (or GTFS-RT/MDS) feeds aggregated by Transitland; filter by spec type and paginate with limit; returns feed id, url, operator, and last fetch status.

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": {
      "spec": "gtfs",
      "limit": 50
    },
    "name": "list_feeds"
  }
}

Input Schema

NameRequiredDescriptionDefault
specNogtfs | gtfs-rt | mds (default gtfs)
limitNo

Output Schema

NameRequiredDescriptionDefault
metaNo
feedsNoList of available feeds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / feeds / items / properties / tags / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
  2. Changed13 schema fields changed
    • addedOutput schema / properties / feeds / items / properties / authorization
      Added value: +{
      +  "properties": {
      +    "info_url": {
      +      "type": "string"
      +    },
      +    "param_name": {
      +      "type": "string"
      +    },
      +    "type": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / feeds / items / properties / feed_state
      Added value: +{
      +  "properties": {
      +    "feed_version": {
      +      "type": [
      +        "null",
      +        "object"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / feeds / items / properties / feed_versions
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "earliest_calendar_date": {
      +        "type": "string"
      +      },
      +      "fetched_at": {
      +        "type": "string"
      +      },
      +      "id": {
      +        "type": "number"
      +      },
      +      "latest_calendar_date": {
      +        "type": "string"
      +      },
      +      "sha1": {
      +        "type": "string"
      +      },
      +      "url": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / feeds / items / properties / id / type
      Previous value: -"string"New value: +"number"
    • addedOutput schema / properties / feeds / items / properties / languages
      Added value: +{
      +  "type": "null"
      +}
    • removedOutput schema / properties / feeds / items / properties / latest_fetch_time
      Removed value: -{
      -  "description": "ISO timestamp of latest fetch",
      -  "type": "string"
      -}
    • addedOutput schema / properties / feeds / items / properties / license
      Added value: +{
      +  "properties": {
      +    "attribution_instructions": {
      +      "type": "string"
      +    },
      +    "attribution_text": {
      +      "type": "string"
      +    },
      +    "commercial_use_allowed": {
      +      "type": "string"
      +    },
      +    "create_derived_product": {
      +      "type": "string"
      +    },
      +    "redistribution_allowed": {
      +      "type": "string"
      +    },
      +    "share_alike_optional": {
      +      "type": "string"
      +    },
      +    "spdx_identifier": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "use_without_attribution": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / feeds / items / properties / name
      Added value: +{
      +  "type": "null"
      +}
    • addedOutput schema / properties / feeds / items / properties / onestop_id
      Added value: +{
      +  "type": "string"
      +}
    • removedOutput schema / properties / feeds / items / properties / operators
      Removed value: -{
      -  "description": "Operators served by this feed",
      -  "items": {
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
    • addedOutput schema / properties / feeds / items / properties / tags
      Added value: +{
      +  "properties": {
      +    "exclude_from_global_query": {
      +      "type": "string"
      +    },
      +    "gtfs_data_exchange": {
      +      "type": "string"
      +    },
      +    "manual_import": {
      +      "type": "string"
      +    },
      +    "notes": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / feeds / items / properties / urls / properties
      Added value: +{
      +  "gbfs_auto_discovery": {
      +    "type": "string"
      +  },
      +  "mds_provider": {
      +    "type": "string"
      +  },
      +  "realtime_alerts": {
      +    "type": "string"
      +  },
      +  "realtime_trip_updates": {
      +    "type": "string"
      +  },
      +  "realtime_vehicle_positions": {
      +    "type": "string"
      +  },
      +  "static_current": {
      +    "type": "string"
      +  },
      +  "static_historic": {
      +    "items": {
      +      "type": [
      +        "string",
      +        null
      +      ]
      +    },
      +    "type": "array"
      +  },
      +  "static_planned": {
      +    "items": {},
      +    "type": "array"
      +  }
      +}
    • addedOutput schema / properties / meta
      Added value: +{
      +  "properties": {
      +    "after": {
      +      "type": "number"
      +    },
      +    "next": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "limit": 50,
      +    "spec": "gtfs"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "Available GTFS/GTFS-RT/MDS feeds",
      +  "properties": {
      +    "feeds": {
      +      "description": "List of available feeds",
      +      "items": {
      +        "properties": {
      +          "id": {
      +            "description": "Transitland feed onestop_id",
      +            "type": "string"
      +          },
      +          "latest_fetch_time": {
      +            "description": "ISO timestamp of latest fetch",
      +            "type": "string"
      +          },
      +          "operators": {
      +            "description": "Operators served by this feed",
      +            "items": {
      +              "type": "object"
      +            },
      +            "type": "array"
      +          },
      +          "spec": {
      +            "description": "Feed specification (gtfs|gtfs-rt|mds)",
      +            "type": "string"
      +          },
      +          "urls": {
      +            "description": "Feed download/access URLs",
      +            "type": "object"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    }
      +  },
      +  "type": "object"
      +}
  4. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare this as read-only, idempotent, and non-destructive. The description adds useful behavioral context by naming the aggregated source, filter/pagination behavior, and specific return fields, which goes beyond what the annotations alone provide.

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?

A single sentence front-loads the core action and then packs in the source, filtering, pagination, and return fields with no filler. Every clause contributes needed information.

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

Completeness5/5

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

For a simple read-only listing tool with only two optional parameters and an output schema, the description covers source, filtering, pagination, and expected return fields. Nothing essential is missing for an agent to invoke it correctly.

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 schema describes the spec values and defaults but leaves limit as a bare number. The description compensates by explaining that limit is for pagination and that spec is a filter, adding meaning beyond the schema fields.

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 the specific verb-resource pair ('List available GTFS... feeds') and adds the Transitland aggregation scope. It does not explicitly contrast with sibling search/list tools, so it stops short of full sibling differentiation.

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 implies use when a broad inventory of feeds is needed, but it gives no explicit guidance about when to prefer this tool over sibling search tools or when not to use it. No alternatives or exclusions are mentioned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.