Skip to main content
Glama

Foodeist

Search restaurants by name

search_restaurants
Read-onlyIdempotent

Find restaurants by (part of) their name, optionally inside one city. Use for "is X any good", "what time does X close".

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": "search_restaurants"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name ("Austin, TX", "London", "Paris, France") or a city slug from find_cities ("austin-tx").
nameYesRestaurant name, e.g. "Franklin Barbecue".
limitNoHow many results (default 5, max 20).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world behavior, so safety is covered. The description adds that matching is on a partial name with optional city scoping, but says nothing about result ordering, tie-breaking on ambiguous names, or default result size, which matter for a search tool.

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?

Two sentences, zero filler: the matching semantics and scope come first, followed by concrete usage triggers. Nothing is repeated from the title or schema, and nothing needs to be trimmed.

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 simple three-parameter read tool with full schema documentation and annotations, the description covers purpose, matching semantics and scoping adequately. The only gap is that with no output schema present, it does not hint at what a result row contains or how many typically come back.

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 baseline is 3, but the description earns a bump by clarifying that 'name' supports partial input — the schema example ('Franklin Barbecue') alone would not tell an agent that substrings are accepted. 'Optionally inside one city' also reinforces that city is a narrowing filter rather than a requirement.

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 verb and resource ('Find restaurants') plus the matching key ('by (part of) their name') and the scoping dimension ('optionally inside one city'). This clearly separates it from proximity- or ranking-based siblings, though it does not explicitly name an alternative tool.

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?

The quoted user phrasings ("is X any good", "what time does X close") give a real routing signal for when to reach for this tool — the user already knows the restaurant's name. However, there is no guidance on when NOT to use it (e.g. browsing, unknown names, or fetching a specific record by id via get_restaurant).

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