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 menu coverage

get_menu_coverage
Read-only

How many venues in each city have menus Dim Hour can stand behind, counted from one menu snapshot. Every city is listed, including cities with none. Each city splits its public venues three ways, and each split covers every venue once: applicability (food or drink venue, not one, or unknown), source (verified_source, unverified_catalog_link, no_link) and completeness (complete, partial, unavailable, requirements_unknown, not_applicable). structured_content counts venues with verified menu sections; fresh_complete counts complete venues whose every verified menu is 90 days old or less at measured_at. These are counts, not a claim that menus are covered. status is unavailable, with no counts, when the menu snapshot does not match the live catalog; reasons names each city that failed.

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": "get_menu_coverage"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoCity name or key. Omit for every city.

Output Schema

NameRequiredDescriptionDefault
noteYes
citiesYes
coversNo
statusYes
reasonsYes
receiptYes
measured_atYes
snapshot_idYes
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

A4/5.0
Behavior5/5

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

The description adds rich behavioral context beyond the read-only annotations: counts come from a single snapshot, every city appears, each venue is split three ways exactly once, structured_content and fresh_complete are precisely defined, and status=unavailable with reasons occurs on snapshot mismatch. This gives the agent a clear picture of what the output means and when data may be missing.

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 description is front-loaded with the core purpose and every sentence carries interpretive value about the counts or status behavior. It is dense but not padded; however, its single-paragraph structure could be made more scannable given the number of distinct field definitions.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only aggregate tool with an output schema, this is complete: it explains the metric, inclusion rule for cities, the three-way split, field semantics, and the unavailable/reasons edge case. An agent has everything needed to call it and interpret the results correctly.

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%, and the city parameter is already documented as 'Omit for every city.' The description reinforces that every city is listed, including cities with none, but adds only marginal parameter-specific meaning beyond the schema; the rest of the text concerns output semantics.

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 states a specific metric and scope: counts of venues with menus per city from one snapshot, including cities with zero. It clearly identifies the resource and aggregation, but it does not explicitly contrast with sibling tools such as get_venue_menus or search_venues, leaving differentiation implicit.

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?

Usage is implied: assess menu coverage across cities. However, there is no explicit guidance on when to use this tool versus alternatives, nor when not to use it. The agent must infer the appropriate context from the purpose alone.

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