Dim Hour

This connector has been deprecated

Superseded by the canonical Dim Hour connector at https://glama.ai/mcp/connectors/com.dimhour.mcp/dim-hour (same server on its branded domain).

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 21,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

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

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"
+]

Changed1 schema field changedAug 25, 2026

changedInput schema / properties / query / description

Previous value: -"Free text matched against name, cuisine, neighborhood, tags, dishes, description"New value: +"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."

Changed1 schema field changedAug 12, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "city": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "scope": {
+      "type": "string"
+    },
+    "showing": {
+      "type": "number"
+    },
+    "total_matches": {
+      "type": "number"
+    },
+    "venues": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "awards": {
+            "type": "string"
+          },
+          "cuisine": {
+            "type": "string"
+          },
+          "description": {
+            "type": "string"
+          },
+          "happy_hour": {
+            "type": "string"
+          },
+          "iconic": {
+            "type": "boolean"
+          },
+          "id": {
+            "type": "number"
+          },
+          "name": {
+            "type": "string"
+          },
+          "neighborhood": {
+            "type": "string"
+          },
+          "opened": {
+            "type": "string"
+          },
+          "price": {
+            "type": "string"
+          },
+          "reservation": {
+            "type": "string"
+          },
+          "score": {
+            "type": "number"
+          },
+          "trending": {
+            "type": "boolean"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "cuisine",
+          "neighborhood",
+          "happy_hour",
+          "reservation",
+          "description",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "total_matches",
+    "showing",
+    "venues"
+  ],
+  "type": "object"
+}

First observedAug 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already establish that this is a non-destructive read operation. Beyond that, the description adds useful behavioral context about ranked results, score range, returned fields, and free-text matching semantics including ignored filler words.

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 description is front-loaded with the core search scope and then covers query behavior and return details efficiently. It is dense but earns most of its length by clarifying high-impact parameters and output expectations.

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 13 optional parameters, full schema coverage, and an output schema, the definition is complete enough for correct invocation. The main remaining gap is lack of explicit differentiation from sibling search/listing tools.

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 schema already documents all 13 parameters thoroughly. The description reinforces city omission and query behavior, but most parameter meaning is duplicated rather than adding substantial new semantics beyond the schema.

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 states a specific verb and resource: searching a restaurant, bar, and venue catalog. It also clarifies the city-scoped versus all-city scope, but it does not distinguish this tool from generic siblings such as `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 gives concrete usage guidance for the key scope decision: pass `city` for one city, omit it to search all 21,000+ venues. It also advises using one strong keyword and combining queries with filters, though it does not explicitly route agents away from sibling search tools.

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?