Skip to main content
Glama

search_restaurant

Look up a US restaurant by name and town from public map listings and, when found, the restaurant's own website menu. Never invents items or prices. Returns a placeToken needed to quote or place an order.

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>",
      "locality": "<locality>"
    },
    "name": "search_restaurant"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
localityYesTown or city, optionally with state

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the lookup sources, the fallback to the restaurant's own menu, and the trust guarantee "Never invents items or prices," which is meaningful behavioral context for an agent. It omits what happens on ambiguous or zero matches and whether results are cached or rate-limited, keeping it short of a 5.

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 what the tool does and the source hierarchy, then the trust guarantee, then the returned token. No filler or redundant restatement of the name.

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 two-parameter lookup with no output schema and no annotations, the description covers purpose, sources, return value, and reliability expectations. The remaining gap is failure and ambiguity behavior (not found, multiple matches), which an agent would need to handle correctly.

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 50%: locality is documented in the schema, name is not. The description compensates partly by clarifying that lookup is by restaurant name and town and constraining locality to US locations, but it adds no format or disambiguation guidance for the bare name parameter.

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 gives a specific verb and resource ("Look up a US restaurant") and pins down both scope (US) and data sources (public map listings, then the restaurant's own website menu). It also states the key output, a placeToken, which makes it clearly distinct from siblings like get_menu or place_order.

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?

The phrase "Returns a placeToken needed to quote or place an order" establishes this as the entry point that must precede quote_order/place_order, so the usage context is clear. However, no sibling is named explicitly and there is no stated when-not guidance (e.g., what to do if the restaurant is already known or a token is already held).

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