Crawlora MCP

subway_available_times

Read-only

Subway store pickup schedule: every time slot the store is currently accepting orders for, as UTC instants from the next orderable time through closing.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "store_id": "<store_id>"
    },
    "name": "subway_available_times"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Optional. Maximum slots to return, 1-200. Defaults to every slot the store offers.
`store_id`	Yes	Required. Store ID from a /subway/store or /subway/nearby result's store_id.

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 7, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuine behavioral context beyond that: results are UTC instants bound to a live ordering window (next orderable time through closing) rather than a static schedule, which is meaningful for a time-sensitive tool.

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; the resource is named first and the scope qualifier follows immediately.

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?

An output schema exists, so return-value structure needn't be described, and annotations cover read-only safety for a 2-param tool. What is present (time semantics, range boundaries) is sufficient; only cross-tool routing guidance 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 coverage is 100%, so both store_id and limit are already documented in the schema (including the 1-200 range and default-to-every-slot behavior). The description's 'every time slot' loosely reflects the default but adds no syntax or format detail. Baseline 3 applies when the schema does the heavy lifting.

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: it returns the time slots a Subway store is currently accepting pickup orders for. The scope ('from the next orderable time through closing') is precise enough that an agent can separate it from subway_store, subway_menu, and subway_nearby without opening a schema.

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 only implied by the phrase 'currently accepting orders for' - it signals this is for live ordering windows, but there is no explicit when-to-use/when-not and no sibling tool named as an alternative. Nothing misleading, but the agent must infer the trigger condition.

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.