Skip to main content
Glama

LoafLoaf Toronto Restaurants

get_restaurant

Read-onlyIdempotent

One restaurant's full profile: weekly hours (and kitchen, brunch, happy-hour hours), price per person, phone, website, how to book (booking platform link, the restaurant's own booking page, or phone), ordering links (own storefront, delivery apps), amenities (reservable, outdoor seating, vegetarian food...) and awards. Takes a few seconds: it reads the restaurant's website for booking and ordering links.

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": {
      "place_id": "<place_id>"
    },
    "name": "get_restaurant"
  }
}

Input Schema

NameRequiredDescriptionDefault
place_idYesplace_id from find_restaurant or search_restaurants.

Output Schema

NameRequiredDescriptionDefault
latNo
lngNo
nameYes
hoursNo
phoneNo
typesYes
awardsYes
ratingNo
addressNo
cuisineNo
sourcesYes
summaryNo
websiteNo
categoryNo
featuresYes
orderingYes
place_idYes
distance_mNo
price_levelNo
price_rangeNo
reservationNo
primary_typeNo
rating_countNo
neighbourhoodNo
short_addressNo
business_statusNo
google_maps_urlNo
secondary_hoursYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the bar is lower, and the description still adds genuinely useful behavior: the call is slow ('takes a few seconds') because it reads the restaurant's website to derive booking and ordering links. That latency and open-world fetch cost is context an agent cannot get from the annotations.

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 resource and purpose, then a compact parenthetical enumeration, then the cost note. It is somewhat dense and the long field list partially duplicates the output schema, but nothing is filler.

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-item lookup with full schema coverage and an output schema, the definition supplies what structured data cannot: the latency warning and the reason for it. The enumerated return fields are arguably redundant given the output schema, but they don't leave the agent under-informed.

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?

The description adds nothing about the single place_id parameter; the schema already documents it at 100% coverage and even names its source tools. Baseline 3 applies since the schema carries the parameter semantics.

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?

States a specific verb+resource combination ('One restaurant's full profile') and enumerates exactly what is returned: hours (including kitchen, brunch, happy-hour), price, phone, website, booking routes, ordering links, amenities, awards. This clearly separates it from the search-style siblings that return multiple restaurants.

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 only implied: the reader infers this is the follow-up detail call after finding a place_id, and the latency note ('takes a few seconds') implicitly discourages bulk use. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. find_restaurant, get_menu) in the description itself.

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