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 menus

get_venue_menus
Read-only

The menus Dim Hour holds for one venue, with the source and date of each. status is verified (menus read from the venue's own site, with sections and prices), link_only (a menu link from the catalog that nobody has verified), no_link, or unavailable. A link_only answer proves nothing about what the menu says. Each menu carries verified_at and a freshness state; past 90 days it is stale, and with no date it is unknown, never fresh. completeness says whether every menu this venue is expected to have is verified; requirements_unknown means nobody has recorded which menus to expect. At most 300 menu items are returned per call; truncated counts the rest. Prices and dishes change: confirm with the venue before relying on them.

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>",
      "id": "<id>"
    },
    "name": "get_venue_menus"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesVenue id from search_venues
cityYesCity name or key
typeNoOnly this menu type, e.g. dinner, brunch, cocktails, wine

Output Schema

NameRequiredDescriptionDefault
idYes
urlYes
cityYes
linkNo
nameYes
menusYes
statusYes
addressYes
reasonsYes
receiptYes
city_nameYes
truncatedNo
snapshot_idYes
completenessYes
requirementsNo
applicabilityYes
missing_typesYes
fresh_completeYes
policy_versionYes
stale_after_daysYes

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

TDQS

A3.9/5.0
Behavior5/5

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

Annotations already declare this a safe, non-destructive, closed read, and the description adds substantive behavior beyond them: a hard cap of 300 menu items per call with a `truncated` count for the remainder, freshness rules (stale past 90 days, unknown rather than fresh when undated), and what `completeness` does and does not guarantee. It also flags the reliability limitation of link_only results and advises confirming prices with the venue. This is exactly the operational context annotations cannot carry.

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 most decision-relevant caveats — staleness and the 300-item truncation — are stated directly, and the sentences are dense but each conveys a distinct rule. It runs long and spends several clauses enumerating status values, which with an output schema present is partly redundant with structured return documentation.

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 read-only lookup with rich annotations and an output schema, the description covers the interpretive gaps an agent actually needs: freshness, completeness guarantees, truncation, and data reliability. The remaining gap is guidance on when to prefer this over sibling coverage/search tools, and the unexplained `type` filter behavior.

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 `id`, `city`, and `type` are already documented, including the example menu types for `type`. The description adds nothing about parameter behavior — notably it never explains how the `type` filter interacts with the returned menus or the truncation count. The baseline 3 applies since the schema carries the full parameter burden.

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 opening sentence names a specific resource and scope: 'The menus Dim Hour holds for one venue, with the source and date of each.' That is a clear verb-less but concrete read action an agent can distinguish from broader searches. It does not, however, distinguish itself from the sibling get_menu_coverage, which appears to concern the same data at a different granularity.

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?

The description implies usage by explaining status semantics ('A link_only answer proves nothing about what the menu says') and warning to 'confirm with the venue before relying on them,' which tells an agent how to act on results. It never states an explicit when-to-use condition or names an alternative such as get_menu_coverage for cross-venue questions, so the guidance remains implied rather than directive.

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