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

search

Read-only

Search Dim Hour's restaurant, bar and venue catalog across all 26 cities. Returns ranked venues with a dimhour.com link for each. Use for questions about where to eat or drink — by cuisine, dish, neighborhood, city, vibe, or award.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	Yes	What to look for, e.g. 'best ramen in NYC', 'michelin dallas', 'rooftop bar miami'

Output Schema

TableJSON Schema

Name	Required	Description	Default
`receipt`	Yes
`results`	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"
+  ]
+}
```

Changed2 schema fields changedSep 17, 2026

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

changedOutput schema / required

Previous value: -[
-  "results"
-]New value: +[
+  "results",
+  "receipt"
+]

AddedAug 11, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already establish readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that results are ranked and each carries a dimhour.com link, which is modest extra value; it says nothing about result counts, pagination, or empty-result behavior. With annotations and an output schema present, a 3 is appropriate.

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?

Two tightly written sentences with the purpose and scope front-loaded and no redundant filler. The '26 cities' detail earns its place as scope; nothing else could be trimmed meaningfully.

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?

Covers purpose, geographic scope, return shape (ranked venues with links), and intended question types; the output schema handles return-value detail. The one real hole is sibling disambiguation against `search_venues`/`find_places`, which matters given the crowded namespace.

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% and the single `query` param already carries examples, so the baseline is 3. The description goes slightly further by naming the facets a query can express (cuisine, dish, neighborhood, city, vibe, award), enriching how an agent should phrase input beyond the schema's three examples.

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') plus scope ('across all 26 cities'). However, it never distinguishes itself from the close siblings `search_venues` and `find_places`, which appear to overlap heavily.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It gives usage context ('Use for questions about where to eat or drink') and enumerates useful search facets (cuisine, dish, neighborhood, city, vibe, award). But with `search_venues`, `find_places`, and `list_*` tools present, the absence of any when-to-use-this-vs-that routing leaves selection ambiguous.

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?