Dim Hour

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 booking options

get_booking_options

Read-only

How to book one venue: its booking platform and link from the Dim Hour catalog. For SevenRooms venues only, given a date, it also returns real bookable times from SevenRooms. Times are a snapshot from SevenRooms at checkedAt. No table is held. Confirm on the booking page before telling anyone it is booked. Other platforms (Resy, OpenTable and the rest) return no times and a times_note saying so.

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_booking_options"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Venue id from search_venues
`city`	Yes	City name or key
`date`	No	Day to check, YYYY-MM-DD. Without it, no times are read.
`party`	No	Party size, 1-20. Default 2.

Output Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`city`	Yes
`name`	Yes
`times`	No
`notice`	No
`receipt`	Yes
`platform`	Yes
`times_note`	No
`booking_url`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already cover the safety profile (readOnly, non-destructive), and the description adds real value on top: times are a stale snapshot taken at checkedAt, no table is held, and the caller must confirm on the booking page before claiming a booking. It also discloses the platform-conditional degradation path (no times + times_note for non-SevenRooms), which an agent could not infer from the schema or annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Roughly five short sentences, front-loaded with what is returned, then the conditional SevenRooms behavior, then the staleness caveat. Nothing is repeated and each sentence carries an operational fact.

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?

An output schema exists, so return structure needn't be re-explained, and the description still names the key nuance fields (checkedAt, times_note) that drive interpretation. For a read-only lookup with a fully documented schema, nothing an agent needs in order to call it correctly is missing.

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 id, date and party are already documented in structured form; the description only reinforces that date drives whether times are read. It adds nothing about party-size semantics or the 1-20 bound, so it sits at the baseline for a fully documented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource: it yields the booking platform and link for one venue from the Dim Hour catalog, then extends to real SevenRooms bookable times when a date is supplied. That scope is clearly separable from siblings like get_venue (venue details) and search_venues (discovery), and it names the id source explicitly.

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 tells the agent the operative condition: times only come back for SevenRooms venues and only when a date is given, while Resy/OpenTable and the rest return no times plus a times_note. What's missing is an explicit when-not/alternative statement (e.g., use get_venue for descriptive details, search_venues to obtain the id), so routing is implied rather than spelled out.

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?