Skip to main content
Glama

Open closed days again

open_days

Opens closed days again for bookings. With unit_id it opens only what was closed for that unit (days closed for all units stay closed); without unit_id it opens every closed day in the range. Part of a longer closed range can be opened; the rest stays closed. 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>",
      "from": "<from>"
    },
    "name": "open_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast night to open (inclusive), YYYY-MM-DD. Default: same as from.
fromYesFirst night to open, YYYY-MM-DD.
addressYesThe venue’s address name, the "name" in name.bookare.app.
unit_idNoLeave out to open the range for all units.
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, closed-world. The description goes beyond that by disclosing the important scoping rule that days closed for all units stay closed when unit_id is given, and that unrelated days in a closed range remain closed. It does not address repeat-invocation behavior (relevant given idempotentHint=false) or what happens if a requested day was never closed.

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 sentences, front-loaded with the action, then the unit_id branching, then the partial-range rule, then venue scope. Nothing is filler, though the closing sentence about address and access key largely restates the schema's required fields.

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?

No output schema exists, and the description covers the tool's semantics, parameter effects, and venue scope adequately for a mutation tool. Gaps are error/edge-case outcomes (day not currently closed, invalid range) and the idempotency implications, which the annotations raise but the text leaves unexplained.

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 100%, so baseline is 3, but the description adds real meaning beyond it: the schema's unit_id note ("Leave out to open the range for all units") is incomplete, and the description clarifies that unit-scoped reopening leaves venue-wide closures intact. It also frames address/access_key as venue targeting rather than merely repeating field names.

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?

States a specific verb and resource ("Opens closed days again for bookings") and immediately scopes it by two distinct modes. An agent can distinguish this from list_closed_days or close_days purely from the description's wording about reopening.

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?

Explicitly explains the conditional choice: supply unit_id to reopen only unit-specific closures, omit it to reopen everything in the range, and notes that part of a longer closed range can be reopened. It does not name the sibling tools (list_closed_days/close_days) as alternatives, which keeps it short of a 5.

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