Yenta Directory

Search menus across venues

search_menus

Read-onlyIdempotent

Find dishes across all venues by text, city, dietary tags or allergens to avoid. Each item is tagged with its venue, so one call compares venues; for one named venue use venue_menu.

Input Schema

Name	Required	Description
`city`	No	Only return items from venues in this city (case-insensitive); call list_cities for the exact values.
`limit`	No	Maximum number of items to return.
`query`	No	Text matched in item name, description, section and menu names; every word must match; connector words (and, with, in) aren't required.
`cursor`	No	Number of items to skip; pass `next_cursor` from the previous page.
`allergens`	No	Exclude items that declare any of these allergens (spelling-insensitive; synonyms match: milk, lactose and dairy all match dairy; pass one term).
`max_price`	No	Only items priced at or under this, in the menu's currency.
`dietary_tags`	No	Require ALL of these dietary tags (case- and separator-insensitive).

Output Schema

Name	Required	Description	Default
`item`	No
`items`	No
`reason`	No
`sample`	No
`source`	No
`status`	Yes
`pagination`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed35 schema fields changedOct 7, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```

changedInput schema / properties / allergens / description

Previous value: -"Exclude items that declare any of these allergens (spelling-insensitive)."New value: +"Exclude items that declare any of these allergens (spelling-insensitive; synonyms match: milk, lactose and dairy all match dairy; pass one term)."

removedInput schema / properties / city / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

addedInput schema / properties / city / type

Added value: +[
+  "string",
+  "null"
+]

addedInput schema / properties / max_price

Added value: +{
+  "default": null,
+  "description": "Only items priced at or under this, in the menu's currency.",
+  "maximum": 1000000,
+  "minimum": 0,
+  "type": [
+    "number",
+    "null"
+  ]
+}

removedInput schema / properties / query / anyOf

Removed value: -[
-  {
-    "maxLength": 256,
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

changedInput schema / properties / query / description

Previous value: -"Text to match against menu item names and descriptions."New value: +"Text matched in item name, description, section and menu names; every word must match; connector words (and, with, in) aren't required."

addedInput schema / properties / query / maxLength
```
Added value: +256
```
addedInput schema / properties / query / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / item / anyOf

Removed value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / item / default
```
Removed value: -null
```
removedOutput schema / properties / item / title
```
Removed value: -"Item"
```
addedOutput schema / properties / item / type
```
Added value: +[
+  "object",
+  "null"
+]
```

removedOutput schema / properties / items / anyOf

Removed value: -[
-  {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / items / default
```
Removed value: -null
```
removedOutput schema / properties / items / title
```
Removed value: -"Items"
```
addedOutput schema / properties / items / type
```
Added value: +[
+  "array",
+  "null"
+]
```

removedOutput schema / properties / pagination / anyOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "description": "The page a paginated read actually served (FR-13, INV-8).\n\n``next_cursor`` is ``None`` both at the end of the results and when the next\ncursor would exceed ``max_public_cursor`` — in either case there is no\nfurther page a caller can legally request.",
-    "properties": {
-      "cursor": {
-        "title": "Cursor",
-        "type": "integer"
-      },
-      "limit": {
-        "title": "Limit",
-        "type": "integer"
-      },
-      "next_cursor": {
-        "anyOf": [
-          {
-            "type": "integer"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "title": "Next Cursor"
-      },
-      "total": {
-        "title": "Total",
-        "type": "integer"
-      }
-    },
-    "required": [
-      "limit",
-      "cursor",
-      "total"
-    ],
-    "title": "Pagination",
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / pagination / default
```
Removed value: -null
```
addedOutput schema / properties / pagination / type
```
Added value: +[
+  "object",
+  "null"
+]
```

removedOutput schema / properties / reason / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / reason / default
```
Removed value: -null
```
removedOutput schema / properties / reason / title
```
Removed value: -"Reason"
```
addedOutput schema / properties / reason / type
```
Added value: +[
+  "string",
+  "null"
+]
```

removedOutput schema / properties / sample / anyOf

Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]

removedOutput schema / properties / sample / default
```
Removed value: -null
```
removedOutput schema / properties / sample / title
```
Removed value: -"Sample"
```
addedOutput schema / properties / sample / type
```
Added value: +[
+  "boolean",
+  "null"
+]
```
removedOutput schema / properties / source / additionalProperties
```
Removed value: -false
```

removedOutput schema / properties / source / description

Removed value: -"FR-13: which approved revision an answer was read from, and how fresh.\n\n``source`` is ``approved-content-revision:<id>`` for every read that answers\nfrom one venue, and the literal ``directory`` for the two cross-venue reads,\nwhich have no single revision to cite."

removedOutput schema / properties / source / properties

Removed value: -{
-  "approved_at": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Approved At"
-  },
-  "content_version": {
-    "title": "Content Version",
-    "type": "integer"
-  },
-  "powered_by": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Powered By"
-  },
-  "source": {
-    "title": "Source",
-    "type": "string"
-  }
-}

removedOutput schema / properties / source / required

Removed value: -[
-  "content_version",
-  "source"
-]

removedOutput schema / properties / source / title
```
Removed value: -"SourceReference"
```
removedOutput schema / properties / status / title
```
Removed value: -"Status"
```
removedOutput schema / title
```
Removed value: -"PublicResponse"
```

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.4/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 genuinely useful behavior beyond that: every returned item is tagged with its venue, which is what makes single-call cross-venue comparison valid. It stops short of describing ordering or pagination mechanics, which the schema partly covers via cursor/next_cursor.

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?

Two tight sentences: the first states scope, the second states the comparison benefit and the alternative tool. No filler, and the differentiator is front-loaded.

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 an output schema present, return values need not be explained, and all seven parameters are optional and fully documented in the schema. The description covers purpose and the sibling alternative adequately; the only mild gap is that it does not state what an unfiltered call returns.

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 is 3. The description restates the main filter axes (text, city, dietary tags, allergens) but adds no syntax, matching semantics, or defaults beyond what the schema already documents (match-all-words, synonym handling, currency, max item counts).

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 (find) and resource (dishes across all venues) and enumerates the discovery axes (text, city, dietary tags, allergens). It also names the sibling it is not (venue_menu) and explains the cross-venue comparison intent, so an agent can distinguish it from venue_menu and search_venues 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit routing rule: multi-venue comparison here, "for one named venue use venue_menu." The city parameter description further points to list_cities for valid values, giving the agent a concrete dependency to resolve before calling.

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?