Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

grubhub_restaurant

Retrieve detailed information for one restaurant using its numeric Grubhub ID, including address, hours, cuisines, rating, delivery options, fees, and coupons.

Instructions

Get one Grubhub restaurant's detail. Returns one Grubhub restaurant: name, address with coordinates, timezone, phone, cuisines, star rating, price tier, whether online ordering is available, whether it offers delivery and pickup, delivery fee, coupon availability, restaurant tags and the full published week of service hours. Note this endpoint publishes fewer economics than GET /grubhub/search -- delivery minimum and the delivery/pickup time estimates come back empty here, so use the search endpoint when you need those.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
restaurant_idYesGrubhub's numeric restaurant id, from /grubhub/search

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are provided, so the description carries the burden. It discloses that certain fields come back empty (delivery minimum, time estimates), which is a meaningful behavioral caveat beyond the schema. It doesn't mention rate limits or auth, but for a read-only detail endpoint the key behavioral gap is covered.

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 two sentences, front-loads the core purpose and return fields, and then adds the caveat about the search endpoint. Every sentence earns its place with no redundancy.

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?

For a single-parameter detail endpoint with no output schema, the description is quite complete: it lists the return fields, notes the missing economics, and points to the alternative. It could mention pagination or response format, but those are less critical for a detail endpoint.

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% and the single parameter is well-described in the schema ('Grubhub's numeric restaurant id, from /grubhub/search'). The description reinforces the source of the ID by referencing the search endpoint, which adds useful provenance beyond the schema.

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 states a specific verb ('Get'), a specific resource ('one Grubhub restaurant's detail'), and enumerates the exact fields returned. It also distinguishes itself from the sibling search endpoint by noting it returns fewer economics, so an agent can tell it apart from grubhub_search and grubhub_restaurant_menu.

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 explicitly says when to use this tool vs the alternative: it notes that delivery minimum and delivery/pickup time estimates come back empty here, and instructs to use the search endpoint when those are needed. This is clear when/when-not guidance.

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