Skip to main content
Glama

Closed days

list_closed_days
Read-onlyIdempotent

Days the venue has closed itself (holiday, own use, an event), for one unit or for all units. Nobody can book those nights, online, by the venue or on connected channels. Defaults to everything from today on. 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>"
    },
    "name": "list_closed_days"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoYYYY-MM-DD. Default: no end.
fromNoYYYY-MM-DD. Default: today.
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

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real context beyond that: the downstream consequence that nobody can book those nights across online, venue, and connected channels, plus the default time window and the one-venue scoping with address and access key. It says nothing about how results are ordered or grouped, which matters for a list tool.

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?

Three short sentences, front-loaded with the resource definition, then booking impact, then scope. The final sentence ('Acts on one venue, given its address and access key') largely restates required parameters and could be cut, but overall there is little wasted text.

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

Completeness3/5

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

For a simple read-only list tool with full schema coverage and no output schema, the definition covers purpose, safety-relevant consequences, and defaults adequately. The gap is the unexplained unit dimension mentioned in the description but absent from the parameters, leaving the agent unsure whether results are per-unit or aggregate and how to narrow to one unit.

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 from, to, address, and access_key are already documented with formats and defaults; the description only echoes the default-from-today behavior. It introduces an unexplained dimension — 'for one unit or for all units' — that has no corresponding parameter in the schema, which muddies rather than clarifies the parameter model. Baseline 3 applies.

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 defines the resource concretely — days the venue has closed itself, citing holiday, own use, and event as causes — which goes beyond a restatement of the name and clarifies what a 'closed day' means. It stops short of an explicit verb like 'list/return' and never names the sibling close_days, so differentiation from the mutation counterpart is left to the tool name alone.

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 only implied: reading existing closures versus the sibling close_days which presumably creates them. The one genuinely useful usage rule is the default window ('Defaults to everything from today on'), which tells the agent what it gets without arguments. There is no explicit when-to-use/when-not-to-use statement or named alternative.

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