Skip to main content
Glama

Set opening hours for bookings

set_opening_hours

Replaces the hours when appointments or tables can be booked. One row per period, several per day allowed (e.g. 10:00-14:00 and 17:00-21:00). Days not listed are closed. For restaurants "to" is the last time a table can be booked. Acts on one venue, given its address and access key.

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": {
      "address": "<address>",
      "access_key": "<access_key>",
      "hours": "<hours>"
    },
    "name": "set_opening_hours"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursYes
addressYesThe venue’s address name, the "name" in name.bookare.app.
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the annotations (which only say it is a non-open-world, non-idempotent write), the description discloses the key behavioral fact that this is a wholesale replacement: existing hours are erased and any weekday omitted is treated as closed. It also clarifies that multiple periods per day are permitted and that scope is one venue identified by address plus access key. It does not state timezone or error behavior, and the 'replaces everything' semantics sit slightly awkwardly next to destructiveHint=false.

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?

Four tight sentences, front-loaded with the replace semantics before the structural detail. The closing sentence about the venue, address and access key largely restates the schema descriptions, which is the only real redundancy.

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 3-parameter mutation with no output schema, the description covers what is overwritten, how periods are structured, what an omitted day means, and how the target venue is identified. Timezone and failure behavior are the remaining gaps, but nothing essential to calling it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, leaving 'from', 'to' and the hours array shape undocumented in the schema, and the description compensates: one row per period, several rows per day allowed, the '10:00-14:00' format example, and the venue-specific meaning of 'to' for restaurants. The weekday closure rule (omitted day = closed) is pure added meaning. It never states the required time string format explicitly or the timezone.

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 first sentence names a specific verb and resource ('Replaces the hours when appointments or tables can be booked') and scopes it to a single venue, so an agent knows exactly what object is written. It doesn't explicitly distinguish itself from the similarly scoped close_days or set_booking_rules siblings, which keeps it from a 5.

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 rather than stated: 'Replaces' and 'Days not listed are closed' tell the agent this is the full-state writer, so partial updates of a single day are not what it does. There is no explicit when-to-use/when-not guidance and no sibling alternative is named (e.g. close_days for temporary closures), so the agent must infer routing.

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