Dim Hour

Get venue details

get_venue

Read-only

Get the full Dim Hour record for one venue: description, signature dishes, address, hours, phone, happy hour, reservation platform, awards, website, Instagram, and (for Iconic 50 venues) the long-form story.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "get_venue"
  }
}

Input Schema

Name	Required	Description
`id`	No	Venue id from search_venues
`city`	Yes	City name or key
`name`	No	Venue name (used if id not given)

Output Schema

Name	Required	Description	Default
`id`	Yes
`lat`	No
`lng`	No
`url`	Yes
`name`	Yes
`tags`	Yes
`hours`	Yes
`phone`	Yes
`price`	No
`score`	No
`story`	No
`awards`	Yes
`dishes`	Yes
`iconic`	No
`opened`	No
`address`	Yes
`cuisine`	Yes
`receipt`	Yes
`website`	Yes
`photoUrl`	Yes
`trending`	No
`city_name`	Yes
`instagram`	Yes
`happy_hour`	Yes
`highlights`	No
`price_tier`	No
`description`	Yes
`reservation`	Yes
`neighborhood`	Yes
`other_locations`	No

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: -[
-  "id",
-  "name",
-  "cuisine",
-  "neighborhood",
-  "tags",
-  "description",
-  "dishes",
-  "happy_hour",
-  "address",
-  "hours",
-  "phone",
-  "reservation",
-  "awards",
-  "website",
-  "instagram",
-  "url",
-  "city_name",
-  "photoUrl"
-]New value: +[
+  "id",
+  "name",
+  "cuisine",
+  "neighborhood",
+  "tags",
+  "description",
+  "dishes",
+  "happy_hour",
+  "address",
+  "hours",
+  "phone",
+  "reservation",
+  "awards",
+  "website",
+  "instagram",
+  "url",
+  "city_name",
+  "photoUrl",
+  "receipt"
+]

First observedSep 6, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds useful context about the breadth of the record and the Iconic 50 long-form story variant, but says nothing about lookup failure behavior or the id-vs-name resolution rule.

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?

A single front-loaded sentence that immediately names the resource and then lists the payload. The field enumeration is long but each item is informative, so it largely earns its place.

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, the description need not explain return values, yet it usefully previews them. Only minor gaps remain: no statement of the id/name fallback logic or what happens when the venue is not found.

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 and the schema already explains id, city, and name, including that id comes from search_venues. The description adds no parameter-level detail beyond noting the Iconic 50 variant.

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 ('Get the full Dim Hour record for one venue') and enumerates the returned fields, making it clear this is a single-record lookup rather than a list. It does not explicitly distinguish itself from siblings like fetch or get_hours, 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 Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of alternatives such as search_venues (which is only referenced inside the schema, not the description). The agent must infer that this is a follow-up to a search.

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?