Skip to main content
Glama

LoafLoaf Toronto Restaurants

find_restaurant

Read-onlyIdempotent

Look up a Toronto restaurant you already have a name for.

Returns candidates, each with name_match (exact | partial | fuzzy | none) and a place_id. An exact match is the restaurant; otherwise check the address. Next: get_restaurant(place_id) or get_menu(place_id).

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe restaurant's name, as the user or a web page wrote it.
nearNoOptional location to disambiguate branches: coordinates, postal code, address or neighbourhood. Without it the name is searched across Toronto.
limitNoMost candidates to return.

Output Schema

NameRequiredDescriptionDefault
nearNo
queryYes
candidatesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral detail: results are candidates rather than a single answer, and each carries a name_match classification with a stated interpretation rule. It stops short of describing empty results or ambiguity handling beyond 'check the address'.

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?

Three short sentences, front-loaded with the one-line purpose before the return shape and the follow-up routing. Every sentence carries distinct information: what it does, what comes back, what to do next.

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 annotations covering safety, full schema coverage on three parameters, and an output schema that documents the return fields, the description only needs to convey purpose, the candidate/match semantics, and the workflow hand-off, all of which it does. Nothing an agent needs in order to call this correctly is missing.

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 description coverage is 100%, so name, near and limit are already documented in the schema, including the disambiguation purpose of near and the maximum of 10. The description adds no syntax or format guidance for near (coordinates vs postal code vs neighbourhood) beyond what the schema states, so the baseline 3 applies.

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 and resource ('look up a Toronto restaurant') and adds a narrowing scope condition ('you already have a name for'), which is what separates it from a free-form restaurant search. It also names the two follow-up tools, so an agent can place it in a workflow without opening any schema.

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?

Gives clear context for use (you have a name in hand) plus a decision rule for the result ('An exact match is the restaurant; otherwise check the address') and explicit next steps to get_restaurant(place_id) or get_menu(place_id). It never says what to do when the name is unknown or what to try when nothing matches, so it falls short of full when/when-not coverage.

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