Skip to main content
Glama

Foodeist

Restaurant menu

get_menu
Read-onlyIdempotent

Menu of one restaurant: sections, dishes, prices, descriptions. Filter by a section or dish keyword to keep it short.

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_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoOnly sections or dishes containing this text, e.g. "vegan", "burger", "dessert".
max_itemsNo
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 covered elsewhere. The description adds relevant context that menus can be long and that filtering/subsetting is the way to bound the response, but says nothing about error behavior for bad slugs or what happens when the menu is empty.

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 compact sentences, front-loaded with what the tool returns, followed by the filtering hint. No filler or repetition; the only shortfall is that it is almost too terse to cover the invocation details.

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 description usefully enumerates the return contents (sections, dishes, prices, descriptions), which is the main thing an agent cannot get from structured fields. Within three parameters and a read-only closed-world operation, this is close to sufficient.

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 67%, and the description explains the intent of the search parameter (section or dish keyword) in plain language, reinforcing the schema examples. It adds nothing about max_items beyond what the schema declares via default 120 and maximum 400, so the marginal value is modest.

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+resource ("Menu of one restaurant") and enumerates the payload it returns: sections, dishes, prices, descriptions. That is enough to tell it apart from get_restaurant or search_restaurants on intent, though it never names those siblings 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?

Offers a concrete usage hint -- filter by section or dish keyword "to keep it short" -- which implies when to use the filter. It gives no explicit guidance on when to call this instead of get_restaurant or search_restaurants, so the routing decision is left implicit.

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