Skip to main content
Glama

LoafLoaf Toronto Restaurants

get_menu

Read-onlyIdempotent

The menu, read from the restaurant's own website: sections and items with prices as printed. Menus that are only images or scanned PDFs come back as attached images for you to read; a result holds a few, and says how to get the rest. Typically 5-90 s the first time (slow sites can take longer), then served from cache for the configured lifetime. website_status explains an empty result (no_menu_found, blocked, robots_disallowed, unreachable...).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
websiteNoThe restaurant's website, when you have it and no place_id.
place_idNoplace_id from find_restaurant or search_restaurants.
media_offsetNoIndex of the first menu image to attach. A result that could not attach every image says which offset to ask for next.

Output Schema

NameRequiredDescriptionDefault
skippedYes
sourcesYes
websiteYes
rendererNo
final_urlNo
fetched_atNo
fetch_countNo
render_callsNo
website_statusNook

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds substantive context beyond them: 5-90 s first-call latency, cache serving afterwards, image-only menus returned as attachments, a bounded number per result, and a documented continuation path via media_offset. It also explains that website_status disambiguates an empty result into no_menu_found, blocked, robots_disallowed, or unreachable.

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?

Front-loaded with the what, then progressive detail on latency, images, and failure modes; no filler sentences. Some clauses are densely packed, but every sentence carries operational information.

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?

For a 3-parameter, output-schema-backed read tool this is thorough: latency expectations, caching, image-only fallback, partial-result paging, and empty-result diagnostics are all covered. An agent has everything needed to call it, wait appropriately, and interpret an empty response.

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 website, place_id, and media_offset are already fully documented in the schema, including the 'when you have it and no place_id' framing and the offset continuation note. The description restates the offset paging behavior without adding format or edge-case detail beyond the schema, so the baseline 3 applies.

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?

States a specific resource and its provenance: sections and items with prices as printed, sourced from the restaurant's own website. That source detail implicitly separates it from the broader get_restaurant sibling, but no sibling is named or explicitly excluded.

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 rather than stated: an agent infers 'call this when you need a menu'. There is no explicit when-not guidance or named alternative, e.g. whether get_restaurant also returns menu data and when to prefer one over the other.

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