Skip to main content
Glama

MICHELIN Guide restaurants for a region and city

travel_michelin_restaurant_guide
Read-only

MICHELIN Guide restaurants for a region and city: restaurant name, distinction (three/two/one star, Bib Gourmand, selected), Green Star flag, price level, cuisine, location text, city, region, coordinates, online booking flag and MICHELIN Guide link; about 48-50 per page (page 1 to 10). Path as in guide.michelin.com/us/en///restaurants. Via a rendering residential proxy. Takes about 42 s; allow a 90 s timeout. Price: $0.02 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "region": "<region>",
      "city": "<city>"
    },
    "name": "travel_michelin_restaurant_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity slug, e.g. new-york, san-francisco, paris, london
pageNoResults page 1 to 10 (default 1)
localeNoSite locale path, default us/en (use fr/fr, gb/en... for other editions)
regionYesGuide region slug, e.g. new-york-state, california, ile-de-france, greater-london

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnlyHint and openWorldHint; the description adds the expensive details an agent actually needs: a rendering residential proxy, ~42 s runtime with a 90 s timeout recommendation, and per-call billing of $0.02 via x402 with failed calls not charged. That pricing and latency disclosure materially changes how an agent should schedule and retry calls.

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?

Purpose and payload are front-loaded, followed by short operational sentences on path, proxy, latency and price. The opening field-list sentence is long and semicolon-heavy, but every clause carries information an agent needs; nothing is 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?

With an output schema present, return values need not be re-explained, and the description covers the remaining risk surface: slug format, pagination ceiling, latency, timeout, billing model and proxy behavior. An agent can budget time and cost and construct a valid call from the description alone.

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 schema already defines all four parameters and their examples. The description still adds value by giving the concrete URL shape that explains the region/city/locale relationship (region is a state/region slug such as ile-de-france, locale selects the edition) and by stating the ~48-50 results-per-page volume that gives 'page' meaning.

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 specific verb+resource ('MICHELIN Guide restaurants for a region and city') and enumerates exactly what comes back: name, distinction tier, Green Star, price, cuisine, location, coordinates, booking flag, guide link. The URL path pattern guide.michelin.com/us/en/<region>/<city>/restaurants pins the resource unambiguously.

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?

It establishes how to scope a call (region + city slugs mirroring the site path), the page range (1 to 10) and the per-page volume (~48-50), which is real operational guidance. It stops short of explicit when-to-use-vs-when-not framing, but for a niche restaurant-guide tool no sibling alternative is obvious.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources