Skip to main content
Glama

Foodeist

Restaurant details

get_restaurant
Read-onlyIdempotent

Everything Foodeist knows about one restaurant: address, phone, website, ratings by source, price level, cuisines, weekly hours and open-now, delivery services, description, what reviewers praise and complain about, menu sections.

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

Input Schema

NameRequiredDescriptionDefault
restaurantYesRestaurant slug, numeric id, or foodeist.com/place/... URL, as returned by the other tools.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely useful scope information (that this is a broad, expensive-looking aggregate including derived review sentiment and open-now status), which helps an agent decide whether it needs this versus a lighter list call. It says nothing about failure behavior for bad slugs or payload size.

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?

A single front-loaded sentence with no filler, and the field enumeration is dense but each item carries signal about what the agent will receive. The colon-separated list is easy to scan even if slightly long.

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?

With no output schema, the field enumeration is the only documentation of return values, and it covers the important ones including derived fields like open-now and review praise/complaints. Adequate for a one-parameter read tool whose annotations already handle safety; only error and size expectations are 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% and the single parameter already documents that it accepts a slug, numeric id, or foodeist.com/place/... URL from other tools. The description adds no further meaning about the identifier, so baseline 3 applies.

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 resource (one restaurant) and enumerates the payload contents: address, phone, website, ratings by source, price level, cuisines, hours, delivery services, review sentiment, menu sections. That distinguishes it in practice from list-oriented siblings like search_restaurants and restaurants_nearby, though it never names them explicitly.

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?

Usage is only implied: 'one restaurant' signals the single-record lookup use case versus the list tools. There is no explicit when-to-use/when-not statement, no mention of what to do if the slug is unknown, and no pointer to get_menu for deeper menu data despite 'menu sections' being listed here.

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