Skip to main content
Glama
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).

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

NameRequiredDescriptionDefault
idNoVenue id from search_venues
cityYesCity name or key
nameNoVenue name (used if id not given)

Output Schema

NameRequiredDescriptionDefault
idYes
latNo
lngNo
urlYes
nameYes
tagsYes
hoursYes
phoneYes
priceNo
scoreNo
storyNo
awardsYes
dishesYes
iconicNo
openedNo
addressYes
cuisineYes
receiptYes
websiteYes
photoUrlYes
trendingNo
city_nameYes
instagramYes
happy_hourYes
highlightsNo
price_tierNo
descriptionYes
reservationYes
neighborhoodYes
other_locationsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / receipt / properties / age_days
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "integer"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • removedOutput schema / properties / receipt / properties / stale
      Removed value: -{
      -  "type": "boolean"
      -}
    • changedOutput schema / properties / receipt / required
      Previous value: -[
      -  "as_of",
      -  "as_of_scope",
      -  "source",
      -  "abstained",
      -  "stale",
      -  "reason"
      -]New value: +[
      +  "as_of",
      +  "as_of_scope",
      +  "source",
      +  "abstained",
      +  "age_days",
      +  "reason"
      +]
  2. Changed1 schema field changed
    • addedOutput schema / properties / receipt / properties / scope_note
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. Changed2 schema fields changed
    • 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"
      +]
  4. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "address": {
      +      "type": "string"
      +    },
      +    "awards": {
      +      "type": "string"
      +    },
      +    "city_name": {
      +      "type": "string"
      +    },
      +    "cuisine": {
      +      "type": "string"
      +    },
      +    "description": {
      +      "type": "string"
      +    },
      +    "dishes": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "happy_hour": {
      +      "type": "string"
      +    },
      +    "highlights": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "hours": {
      +      "type": "string"
      +    },
      +    "iconic": {
      +      "type": "boolean"
      +    },
      +    "id": {
      +      "type": "number"
      +    },
      +    "instagram": {
      +      "type": "string"
      +    },
      +    "lat": {
      +      "type": "number"
      +    },
      +    "lng": {
      +      "type": "number"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "neighborhood": {
      +      "type": "string"
      +    },
      +    "opened": {
      +      "type": "string"
      +    },
      +    "other_locations": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "phone": {
      +      "type": "string"
      +    },
      +    "photoUrl": {
      +      "type": "string"
      +    },
      +    "price": {
      +      "type": "string"
      +    },
      +    "price_tier": {
      +      "type": "number"
      +    },
      +    "reservation": {
      +      "type": "string"
      +    },
      +    "score": {
      +      "type": "number"
      +    },
      +    "story": {
      +      "type": "string"
      +    },
      +    "tags": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "trending": {
      +      "type": "boolean"
      +    },
      +    "url": {
      +      "type": "string"
      +    },
      +    "website": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "name",
      +    "cuisine",
      +    "neighborhood",
      +    "tags",
      +    "description",
      +    "dishes",
      +    "happy_hour",
      +    "address",
      +    "hours",
      +    "phone",
      +    "reservation",
      +    "awards",
      +    "website",
      +    "instagram",
      +    "url",
      +    "city_name",
      +    "photoUrl"
      +  ],
      +  "type": "object"
      +}
  5. First observed

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, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: it discloses the field set returned and flags conditional content ('for Iconic 50 venues') that only appears for a subset of venues. It says nothing about permissions, rate limits, or failure behavior, though those are minor for a read-only lookup.

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 with the core action first and the field enumeration after. The long field list is long but earns its place by telling the agent what information is retrievable, avoiding a follow-up call.

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?

An output schema exists, so return values do not need spelling out, yet the description still previews them usefully. For a simple three-parameter read-only lookup this is essentially complete; the only loose end is the unexplained 'Iconic 50' qualification, which the agent can safely treat as conditional data presence.

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 explains id, city, and name, including that name is used if id is not given. The description adds no parameter guidance of its own — notably it does not restate the id-precedence or that city is required even when id is supplied. 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 uses a specific verb and resource ('Get the full Dim Hour record for one venue') and enumerates the returned fields, so the agent knows exactly what this resolves. It stops short of distinguishing itself from siblings that overlap on returned data (get_hours, get_venue_menus), which are implicitly bundled into this 'full record'.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative tool is named. The phrase 'full ... record' weakly implies 'use for comprehensive details rather than search', but that is left for the agent to infer.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources