Skip to main content
Glama

Foodeist

Search Foodeist

search
Read-onlyIdempotent

Free-text search over Foodeist restaurants. Understands " in " ("best tacos in Austin", "Joe's Pizza in New York") and plain restaurant names. Returns ids to pass to fetch. Prefer top_restaurants / search_restaurants when you can fill their fields.

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": {
      "query": "<query>"
    },
    "name": "search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesWhat the user is looking for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so safety is covered. The description adds behavior the annotations cannot: it parses natural-language query patterns and returns ids rather than records, making the fetch handoff explicit. It does not mention empty-result or fuzzy-match behavior, which keeps it short of a 5.

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?

Three sentences, no filler, and the core capability plus query syntax are front-loaded ahead of the alternative-routing note. Every clause carries information the agent needs to either call the tool or not.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter, annotation-rich search tool with no output schema, the definition covers purpose, query shape, return value (ids), and the fetch handoff. Nothing an agent needs to invoke it correctly is missing.

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?

The single parameter is fully documented in the schema, so the baseline is 3. The description earns above baseline by specifying the accepted query grammar and giving concrete examples, which tells the agent how to shape the string rather than just that it is "what the user is looking for."

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Free-text search over Foodeist restaurants") and immediately scopes what the free text can express ("<cuisine or name> in <city>", plain names). An agent can distinguish it from search_restaurants/top_restaurants without opening either schema.

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?

"Prefer top_restaurants / search_restaurants when you can fill their fields" gives an explicit alternative and the condition that selects it, plus "Returns ids to pass to fetch" documents the downstream chaining step. The selection criterion is slightly soft ("when you can fill their fields"), but the routing intent is unambiguous.

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