Dim Hour

Search venues

search_venues

Read-only

Search Dim Hour's restaurant, bar and venue catalog. Pass city to search one city, or OMIT city to search more than 20,000 venues across every city at once (e.g. 'best ramen anywhere', 'michelin spots'). Returns ranked matches with score (0-100 quality), price tier, neighborhood, happy-hour info, and a dimhour.com link. Free-text query matches each content word individually across cuisine, dish, vibe, and name (filler like 'best' or 'tonight' is ignored) - one strong keyword beats a sentence; combine with filters.

Input Schema

TableJSON Schema

Name	Required	Description
`city`	No	City name or key, e.g. 'NYC', 'dallas'. OMIT to search ALL cities at once.
`sort`	No	Result order. Default score_desc (highest quality first).
`limit`	No	Max results, default 10
`query`	No	Free text; every content word must appear in name, cuisine, neighborhood, tags, dishes, or description (filler like 'best'/'tonight' is ignored). One strong keyword beats a full sentence.
`fields`	No	Return only these fields on each venue, to keep a result small. `id`, `name` and `url` are always included — `url` is the citation link.
`cuisine`	No	Filter to a cuisine (substring match)
`max_price`	No	Max price tier 1-4 ($-$$$$)
`min_score`	No	Minimum quality score 0-100
`iconic_only`	No	Only 'Iconic 50' venues (NYC has these today)
`neighborhood`	No	Filter to a neighborhood (substring match)
`trending_only`	No	Only trending venues
`awards_contains`	No	Only venues whose awards field matches, e.g. 'michelin', 'james beard', 'bib gourmand'
`happy_hour_only`	No	Only venues with happy hour info

Output Schema

TableJSON Schema

Name	Required	Description	Default
`city`	No
`note`	No
`scope`	No
`venues`	Yes
`receipt`	Yes
`showing`	Yes
`total_exact`	Yes
`total_matches`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 3, 2026
- addedOutput schema / properties / receipt / properties / scope_note
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

Changed5 schema fields changedSep 17, 2026

addedInput schema / properties / fields

Added value: +{
+  "description": "Return only these fields on each venue, to keep a result small. `id`, `name` and `url` are always included — `url` is the citation link.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "Result order. Default score_desc (highest quality first).",
+  "enum": [
+    "score_desc",
+    "score_asc",
+    "name_asc"
+  ],
+  "type": "string"
+}

addedOutput schema / properties / receipt

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "abstained": {
+      "type": "boolean"
+    },
+    "as_of": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "as_of_scope": {
+      "type": "string"
+    },
+    "reason": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "source": {
+      "type": "string"
+    },
+    "stale": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "as_of",
+    "as_of_scope",
+    "source",
+    "abstained",
+    "stale",
+    "reason"
+  ],
+  "type": "object"
+}

addedOutput schema / properties / total_exact
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / required

Previous value: -[
-  "total_matches",
-  "showing",
-  "venues"
-]New value: +[
+  "total_matches",
+  "total_exact",
+  "showing",
+  "venues",
+  "receipt"
+]

First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed (non-open-world) catalog, so the safety profile is covered. The description adds useful behavioral detail beyond that: the ranked return shape (score, price tier, neighborhood, happy hour, citation link) and the fact that queries are tokenized word-by-word with filler ignored.

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?

Three dense sentences, front-loaded with purpose then scope then query mechanics; nothing is padded. It is slightly information-packed, but each clause carries actionable signal.

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 13-parameter, optional-only search tool with an output schema present, the description covers scope, query semantics, return contents, and filter combination. Nothing an agent needs to call 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?

Schema coverage is 100%, so the baseline is 3. The description goes further by explaining the query matching model ('one strong keyword beats a sentence') and the cross-parameter interaction with filters, which helps an agent compose calls rather than just fill fields.

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 and resource ('Search Dim Hour's restaurant, bar and venue catalog') and immediately clarifies the two search scopes (one city vs all cities). It does not explicitly differentiate itself from close siblings like `search`, `find_places`, or `get_venue`, so it stops short of a 5.

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?

Gives clear operational guidance: pass `city` for one city, OMIT it for the 20k-venue global sweep, with example intents. It does not say when to prefer this tool over `find_places` or `search`, so there is no explicit alternative routing.

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

All Dim Hour 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?