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 every venue 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.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_venues"
  }
}

Input 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 in every result, whatever you ask for — `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

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.

Changed2 schema fields changedNov 10, 2026

changedInput schema / properties / fields / description

Previous value: -"Return only these fields on each venue, to keep a result small. `id`, `name` and `url` are always included — `url` is the citation link."New value: +"Return only these fields on each venue, to keep a result small. `id`, `name` and `url` are in every result, whatever you ask for — `url` is the citation link."

changedOutput schema / properties / venues / items / required

Previous value: -[
-  "id",
-  "name",
-  "cuisine",
-  "neighborhood",
-  "happy_hour",
-  "reservation",
-  "description",
-  "url"
-]New value: +[
+  "id",
+  "name",
+  "url"
+]

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

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint false), but the description adds real behavior: ranked results scored 0-100 quality, and the token-matching rule that each content word must match cuisine, dish, vibe, or name while filler like 'best' is ignored. Return-field detail is partly redundant with the output schema, which keeps it from 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The most important routing rule (city present vs. omitted) is front-loaded in the first sentence, and the rest is dense with no filler. The parentheticals and long second sentence are slightly dense but each clause carries information.

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?

For a 13-parameter search tool with a full output schema and annotations, the description covers the routing decision, matching semantics, and result shape adequately. The ten filter parameters are left entirely to the schema, which is acceptable at 100% coverage.

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 100%, so the schema already documents every parameter including city omission and query matching. The description reiterates those and adds only marginal guidance ('one strong keyword beats a sentence'). With the schema doing the heavy lifting, the baseline 3 applies.

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?

The description opens with a specific verb and resource: 'Search Dim Hour's restaurant, bar and venue catalog.' The city-scoping sentence makes the breadth of the search explicit ('every venue across every city at once'). It never names a sibling tool, so an agent must infer the difference from tools like search or find_places.

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?

It clearly states the two usage modes: pass `city` to search one city, or omit it to search everywhere, with example intents ('best ramen anywhere', 'michelin spots'). It also advises on query strategy ('one strong keyword beats a sentence; combine with filters'). It offers no explicit when-not or alternative-tool 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?