Crawlora MCP

subway_nearby

Read-only

Subway store proximity search by coordinate or free-text address/city/ZIP, or a direct lookup by store id: distance, live open status, payment methods, catering link and feature flags.

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": "subway_nearby"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Optional. Maximum stores to return, 1-20, default 10.
`query`	No	Free-text address, city or ZIP to search near. Alternative to latitude/longitude.
`offset`	No	Optional. Opaque pagination cursor from a previous response's next_offset.
`features`	No	Optional, comma-separated. Restricts results to stores with ALL listed features. Allowed values: HAS_BREAKFAST, IS_REMOTEORDER_ACCEPTED, HAS_HALAL, HAS_DRIVETHROUGH, HAS_CATERING, HAS_CURBSIDE, IS_OPERATING.
`latitude`	No	Search center latitude. Set together with longitude, or set query instead -- exactly one search mode.
`store_id`	No	Look up one store directly by its store_id (from /subway/store or a prior /subway/nearby result). Alternative to latitude/longitude and query -- exactly one search mode.
`longitude`	No	Search center longitude.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context about what comes back (distance, live open status, payment methods, catering link, feature flags), though it omits pagination/limit behavior implied by the schema params.

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 front-loaded sentence with no filler, covering modes first and returned data second. Every clause earns its place.

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 an output schema exists and annotations cover read-only/open-world behavior, the description is nearly complete; it even previews returned fields. Only minor gaps remain around mode exclusivity enforcement and pagination behavior, which the schema covers indirectly.

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 limit, query, cursor, features, latitude/longitude and store_id. The description echoes the mutually exclusive search modes but adds no syntax or format detail beyond what the schema provides; baseline 3 is appropriate.

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 (proximity search) and resource (Subway store), then enumerates all three input modes (coordinate, free-text address/city/ZIP, direct store-id lookup) and the returned facets. An agent can immediately tell this apart from siblings like subway_store or subway_menu.

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?

The three search modes are clearly described so an agent knows when to pass coordinates vs query vs store_id, and the schema reinforces 'exactly one search mode'. However, it does not explicitly name or exclude sibling tools, so sibling differentiation is left implicit.

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

All Crawlora MCP 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.

Resources

Need Help?