Yenta Directory

Search a venue's menu by name

venue_menu_search

Read-onlyIdempotent

Search a named venue's menu by text, required dietary tags and allergens to avoid; call venue_dietary_options first for the exact spellings (the venue's own host calls this search_menu).

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	Disambiguate a name by city (call list_cities); ignored for a slug.
`limit`	No	Maximum number of items to return.
`query`	No	Text to match against item names and descriptions.
`venue`	Yes	Venue name or slug; call search_venues to discover one.
`cursor`	No	Number of items to skip; pass `next_cursor` from the previous page.
`allergens`	No	Exclude items declaring any of these allergens (exact spelling).
`dietary_tags`	No	Require ALL of these tags (exact spelling from venue_dietary_options).

Output Schema

TableJSON Schema

Name	Required	Description
`item`	No
`items`	No
`reason`	No
`sample`	No
`source`	No	FR-13: which approved revision an answer was read from, and how fresh. ``source`` is ``approved-content-revision:<id>`` for every read that answers from one venue, and the literal ``directory`` for the two cross-venue reads, which have no single revision to cite.
`status`	Yes
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 23, 2026

addedInput schema / properties / allergens / maxItems
```
Added value: +8
```
addedInput schema / properties / dietary_tags / maxItems
```
Added value: +8
```

changedInput schema / properties / query / anyOf

Previous value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maxLength": 256,
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / sample

Added value: +{
+  "anyOf": [
+    {
+      "type": "boolean"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Sample"
+}

First observedSep 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable behavioral context beyond that: the requirement to use exact spellings from a prior call, and the fact that the venue's own host exposes this as search_menu—useful for mapping terminology across systems.

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?

A single sentence that leads with the core action and resources, then adds the critical prerequisite and naming context. Every clause earns its place, and there is no redundant repetition of schema content.

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?

With a rich input schema, a full output schema, and strong safety annotations, the description only needs to add selection guidance and cross-tool dependencies. It does exactly that by naming venue_dietary_options as a prerequisite and clarifying the host-side alias. Nothing essential is missing for correct invocation.

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%, so the baseline of 3 applies. The description's phrase 'required dietary tags and allergens to avoid' restates the schema semantics but does not add new parameter details; the schema already documents exact-spelling requirements, limits, cursor pagination, and city disambiguation.

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?

The description states a specific verb ('search') and resource ('a named venue's menu'), and enumerates the filter dimensions: text, dietary tags, and allergens to avoid. It is clearly distinct from global sibling tools like search_menus, and the parenthetical host alias further disambiguates its identity.

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?

The description gives explicit usage context by instructing the agent to call venue_dietary_options first to obtain exact spellings, which prevents common parameter-value errors. It does not spell out when not to use this tool versus siblings like search_menus, but the prerequisite guidance is clear and actionable.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Yenta Directory tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?