Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

subway_sitemap

Enumerate Subway store locations by paging through sitemap shards. Returns URLs for country, region, city, and street pages.

Instructions

Browse Subway's global store-URL index. Returns one page of Subway's sitemap-declared store index -- 22,700+ URLs across 2 shards at time of writing, covering a country/region/city/street tree worldwide. This is the cheapest way to enumerate Subway locations. Each entry carries its URL, the locator path GET /subway/store takes, and a depth: the deepest entries are store pages, shallower ones are country, region and city directory pages listed in the same sitemap. A page past the end returns an empty list rather than an error, so a caller can walk to exhaustion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo1-based page within the shard (default 1)
shardNoSitemap shard index (default 0). shard_count in the response says how many exist.
page_sizeNoEntries per page, 1-500 (default 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations the description carries the full behavioral burden, and it does well: it discloses pagination semantics (one page per call), the past-the-end empty-list behavior enabling walk-to-exhaustion, shard count, and per-entry structure including the depth meaning. It does not explicitly state read-only/no-auth, so it falls short of the highest bar.

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?

Front-loads the resource and the practical scale, then unpacks entry structure and pagination edge case. Slightly dense but every sentence carries information; no filler.

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?

With no output schema, the description usefully describes what an entry contains (URL, locator path, depth) and the empty-page termination rule, covering the essentials for correct invocation and traversal. Minor gap: no explicit statement on permissions or rate limits.

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 page, shard, and page_size. The description adds surrounding context (shard_count in response, depth) but no added syntax or defaults beyond the schema. 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+resource: browsing Subway's global store-URL index / sitemap-declared store index. It clearly frames the return (URLs) and scope (worldwide country/region/city/street tree), which distinguishes it from nearby store or menu tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

"This is the cheapest way to enumerate Subway locations" gives a comparative reason to pick this tool over alternatives. It does not explicitly name sibling tools (subway_nearby, subway_store) as the excluded alternatives, so guidance is clear but not fully routing.

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