Skip to main content
Glama

Close days

close_days

Makes one day or a whole range unavailable, for one unit or (without unit_id) for all units: no bookings can be made on those nights, online, by the venue or on connected channels. A closed day means nobody can stay that night. Existing bookings on those days are not cancelled; they are listed in the answer. For one day, send only from. 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": "close_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast closed night (inclusive), YYYY-MM-DD. Default: same as from.
fromYesFirst closed night, YYYY-MM-DD.
reasonNoOptional, only the venue sees it, e.g. "Holiday" or "Family visit".
addressYesThe venue’s address name, the "name" in name.bookare.app.
unit_idNoLeave out to close all units.
access_keyYesThe venue’s access key.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations only declare non-read-only and non-destructive; the description goes well beyond that by explaining what the operation blocks, that existing bookings survive, and that affected bookings appear in the response. It leaves out whether repeating the call is harmless (relevant given idempotentHint=false) and how to undo it, so it is strong but not exhaustive.

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 short sentences, front-loaded with the core effect and followed by scope rules and the booking caveat. No filler, though the venue/access-key sentence at the end is mildly redundant with the schema.

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 compensates by stating that existing bookings are returned in the answer. For a scoped mutation tool it covers effect, scope, and side effects adequately; only reversibility and idempotency behavior are unaddressed.

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 all six parameters are already documented, including the default for 'to'. The description adds only the practical rule 'for one day, send only from' and the all-units behavior of omitting unit_id, which is largely a restatement of the 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?

States a specific verb and resource (make a day or range unavailable) plus the exact scope: one unit when unit_id is given, all units otherwise. The consequence (no bookings can be made on those nights, across online, venue, and connected channels) makes the tool's effect unmistakable and separates it from a listing tool.

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?

Gives concrete invocation guidance: 'For one day, send only from' and 'without unit_id ... for all units'. It also clarifies the important precondition that existing bookings are not cancelled. It does not explicitly name the inverse tool (open_days) as an alternative, 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