Skip to main content
Glama

Foodeist

Restaurants near a point

restaurants_nearby
Read-onlyIdempotent

Restaurants around coordinates, best first (or nearest first). Use when the user gives a location, address you can geocode, or "near me" with coordinates.

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": {
      "lat": "<lat>",
      "lng": "<lng>"
    },
    "name": "restaurants_nearby"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lngYes
sortNobest
limitNoHow many results (default 10, max 30).
cuisineNoCuisine or dish type, e.g. "pizza", "sushi", "mexican", "steakhouse", "vegan", "coffee".
open_nowNoOnly places open right now (by their local time).
radius_mNoSearch radius in meters (default 1500, max 10000).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorldHint=false, so the safety profile is covered. The description adds that results are ordered best-first by default and that an address can be geocoded, which is useful. It omits whether results are paginated, how ranking 'best' is computed, and whether prices/ratings are returned, so it adds only modest context.

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?

Two tight sentences with the core behavior front-loaded and the usage trigger second. No filler, though the parenthetical '(or nearest first)' is slightly awkward phrasing for what is really the sort parameter.

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 7-parameter read tool with no output schema, the description covers the anchor and ordering but says nothing about the filtering surface (cuisine, open_now, radius_m) or what a result contains. An agent asked for 'open-now pizza nearby' would not learn from the description that this tool supports those constraints.

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 57%, with limit, cuisine, open_now, and radius_m self-documented. The description contributes the meaning of the 'best' vs 'nearest' sort options and implies lat/lng can come from geocoding an address, but it never mentions the cuisine, open_now, or radius filters that materially change results.

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 the resource (restaurants) and the anchor (around coordinates), plus the ordering behavior ('best first (or nearest first)'). The verb is implicit rather than stated, and nothing distinguishes it from sibling search_restaurants or top_restaurants, so an agent cannot rule those out from the text alone.

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?

Gives a when-to-use trigger: the user supplies a location, a geocodable address, or 'near me' with coordinates. That is real positive guidance, but there are no exclusions and no routing to siblings like search_restaurants, whose distinction from this tool stays unclear.

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