Skip to main content
Glama

Foodeist

Top restaurants in a city

top_restaurants
Read-onlyIdempotent

Best-ranked restaurants in a city by the Foodeist ranking, optionally only one cuisine. Answers "best X in Y" questions.

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

Input Schema

NameRequiredDescriptionDefault
cityYesCity name ("Austin, TX", "London", "Paris, France") or a city slug from find_cities ("austin-tx").
limitNoHow many results (default 10, max 30).
cuisineNoCuisine or dish type, e.g. "pizza", "sushi", "mexican", "steakhouse", "vegan", "coffee".

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 readOnly, idempotent, and non-destructive behavior, so safety is covered. The description adds that results come from a specific ranking and that the cuisine filter is optional/single-value, but says nothing about result ordering guarantees beyond the ranking or about what a result record contains.

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 short sentences, front-loaded with the core purpose and followed by the routing cue. No filler or restated title text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 annotation coverage, this is nearly sufficient, but with no output schema the description never indicates what a result contains (name, rating, address) or how many/which fields an agent can rely on.

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 all three parameters are already documented with examples and bounds. The description adds only the nuance that the cuisine filter is optional and limited to a single cuisine; the city and limit parameters gain nothing beyond the schema.

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?

Names a specific verb (ranked listing) and resource (restaurants in a city) and states the ranking basis (Foodeist ranking), which distinguishes it from proximity- or keyword-based siblings. It stops short of naming an alternative sibling, but the scope is unambiguous.

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?

"Answers 'best X in Y' questions" gives a concrete query pattern that selects this tool over a nearby-search or keyword-search sibling. There is no explicit when-not guidance, but the intended context is clear.

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