Crawlora MCP

grubhub_timepicker

Read-only

Grubhub restaurant future orderable time-slot calendar: every delivery or pickup slot available up to 7 days ahead, as timestamps with the restaurant's real UTC offset resolved (DST-correct).

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": {
      "restaurant_id": "<restaurant_id>",
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "location_mode": "<location_mode>"
    },
    "name": "grubhub_timepicker"
  }
}

Input Schema

Name	Required	Description
`days`	No	Optional. How many days ahead to fetch, 1-7. Default 7.
`latitude`	Yes	Required. Diner location latitude.
`longitude`	Yes	Required. Diner location longitude.
`location_mode`	Yes	Required. One of DELIVERY, PICKUP.
`restaurant_id`	Yes	Required. Grubhub restaurant 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 5, 2026

TDQS

A3.7/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 genuinely useful behavioral detail beyond that: timestamps carry the restaurant's real UTC offset and are DST-correct, and the horizon is capped at 7 days. This is the kind of semantic context annotations cannot express.

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?

A single dense sentence that front-loads the resource and scope. Every clause earns its place, though it packs several ideas (scope, horizon, timestamp format) into one sentence without structural breaks.

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 an output schema present, annotations covering safety, and full parameter documentation, the description only needs to convey scope and behavioral quirks — which it does via the DST-correct UTC offset and 7-day cap. It is essentially complete for a read-only listing tool, missing only sibling routing cues.

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% and every parameter is documented in the schema, so the baseline is 3. The description loosely echoes the days horizon ('up to 7 days ahead') and the DELIVERY/PICKUP dimension, but adds no syntax or format detail beyond what the schema already states.

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 names a specific resource (future orderable time-slot calendar) and its scope (every delivery or pickup slot up to 7 days ahead), so the agent knows exactly what is returned. It does not explicitly differentiate itself from the sibling grubhub_availability or grubhub_restaurant_menu, leaving the agent to infer which endpoint to pick.

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 resource name — use it to see future orderable slots — but there is no explicit when-to-use, when-not-to-use, or alternative named (e.g., grubhub_availability). The agent must infer the routing decision on its own.

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?