Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

grubhub_timepicker

Retrieve a restaurant's full delivery or pickup time-slot calendar for up to 7 days ahead, with precise timestamps and UTC offsets, to build a scheduling picker.

Instructions

Get one Grubhub restaurant's future orderable time-slot calendar. Returns every future delivery or pickup time slot Grubhub will accept an order for, up to 7 days ahead. This is what powers the site's own "schedule my order" picker: /grubhub/availability tells you whether a restaurant is orderable right now plus one "next" time, while this returns the full future slot calendar a caller would need to build an actual date-and-time picker. Slots are grouped by date and given as full timestamps carrying the restaurant's real UTC offset for that instant, so a caller never has to resolve daylight-saving transitions themselves. Requesting location_mode=DELIVERY returns delivery slots only; PICKUP returns pickup slots only -- the upstream only computes one side per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoHow many days ahead to fetch, 1-7 (default 7)
latitudeYesDiner location latitude
longitudeYesDiner location longitude
location_modeYesWhich slot grid to return
restaurant_idYesGrubhub restaurant id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / location_mode / enum
      Added value: +[
+  "DELIVERY",
+  "PICKUP"
+]
  2. Addedv1.16.2

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden, and it goes well beyond a generic 'get' statement. It discloses the 7-day horizon, grouping by date, full timestamps with the restaurant's real UTC offset, automatic DST handling, and the upstream limitation of computing only one location mode per call.

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?

The description is dense but every sentence earns its place: it states the core action, defines the return scope, contrasts with a sibling tool, explains the timestamp/timezone behavior, and clarifies the location_mode constraint. There is no filler.

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?

There is no output schema, but the description compensates by explaining the return nature: full future slots, grouped by date, with DST-safe timestamps. Combined with the schema's detailed parameters, an agent has enough information to invoke the tool correctly and interpret the result.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful value for location_mode by specifying that DELIVERY returns only delivery slots, PICKUP only pickup slots, and that the upstream computes one side per call. It also reinforces the days parameter's meaning with 'up to 7 days ahead.'

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?

The description opens with a precise verb and resource: 'Get one Grubhub restaurant's future orderable time-slot calendar.' It explains exactly what is returned—every future delivery or pickup slot up to 7 days ahead—and explicitly contrasts itself with /grubhub/availability, making its purpose unambiguous.

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

Usage Guidelines5/5

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

The description provides clear decision guidance: use this tool when the full future slot calendar is needed to build a date-and-time picker, versus /grubhub/availability for immediate orderability and a single 'next' time. It also explains the location_mode constraint so the caller knows one side must be requested per call.

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