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).

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

NameRequiredDescriptionDefault
cityNoCity name or key, e.g. 'NYC', 'dallas'. OMIT to search ALL cities at once.
sortNoResult order. Default score_desc (highest quality first).
limitNoMax results, default 10
queryNoFree 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.
fieldsNoReturn 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.
cuisineNoFilter to a cuisine (substring match)
max_priceNoMax price tier 1-4 ($-$$$$)
min_scoreNoMinimum quality score 0-100
iconic_onlyNoOnly 'Iconic 50' venues (NYC has these today)
neighborhoodNoFilter to a neighborhood (substring match)
trending_onlyNoOnly trending venues
awards_containsNoOnly venues whose awards field matches, e.g. 'michelin', 'james beard', 'bib gourmand'
happy_hour_onlyNoOnly venues with happy hour info

Output Schema

NameRequiredDescriptionDefault
cityNo
noteNo
scopeNo
venuesYes
receiptYes
showingYes
total_exactYes
total_matchesYes

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. Changed2 schema fields changed
    • 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"
      +]
  3. Changed1 schema field changed
    • addedOutput schema / properties / receipt / properties / scope_note
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  4. Changed5 schema fields changed
    • 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"
      +]
  5. Changed1 schema field changed
    • 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."
  6. Changed1 schema field changed
    • 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"
      +}
  7. First observed

TDQS

A3.9/5.0
Behavior4/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 real behavioral context beyond that — result ranking, the score/price/neighborhood/happy-hour/link payload, and how content words are matched with filler ignored. It doesn't state pagination or result-count behavior beyond the `limit` cap, which is already in the schema.

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?

It's a single dense paragraph, but the most consequential fact (omit city = all cities) is front-loaded in sentence two, and the query-semantics guidance follows logically. The parenthetical examples and the 'one strong keyword beats a sentence' tip earn their place rather than padding.

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, zero-required search tool with a full schema and an output schema, the description covers the scope decision, ranking, and query behavior an agent needs to call it correctly. Return-value detail is appropriately deferred to the output schema rather than duplicated.

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 baseline is 3. The description does meaningfully reinforce the highest-risk semantic — omitting `city` searches everything — and explains the free-text matching model (per content word, filler ignored), which is genuinely useful nuance the schema only partly conveys.

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 names a specific verb and resource — search Dim Hour's restaurant, bar and venue catalog — and immediately frames the scope decision (one city vs. all cities). It does not explicitly contrast itself with siblings like 'search', 'find_places' or 'get_venue', so an agent must infer that this is the broad catalog search rather than a single-venue lookup.

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 when-to guidance: pass `city` to search one city, omit it to search all cities, and use example phrasings ('best ramen anywhere', 'michelin spots') to signal the all-cities case. It also advises combining free text with filters and that one strong keyword beats a sentence, but names no alternative tool for narrowing to a single venue or listing cities.

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