Skip to main content
Glama

Change booking rules

set_booking_rules

Sets how many hours before a class a member can cancel free, how many classes can be booked on an unpaid pack, and how many days ahead members can book. Only the fields you send change. 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": "set_booking_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
access_keyYesThe venue’s access key.
days_ahead_members_can_bookNo1-60
free_cancellation_hours_beforeNo0-168
bookings_allowed_on_unpaid_packNo0-50

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Adds two genuinely useful behavioral facts beyond the annotations: partial-update semantics ("Only the fields you send change") and the targeting/auth model (one venue, addressed by address plus access key). It does not cover validation failure behavior or whether prior values are recoverable, but with destructiveHint=false and openWorldHint=false already declared, the remaining gap is minor.

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?

Three sentences, zero filler, and the core effect is front-loaded followed by the two caveats an agent most needs (partial update, single-venue targeting). Nothing restates the title or the parameter names verbatim without adding meaning.

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 5-parameter mutation with full schema coverage and no output schema, the description covers purpose, patch semantics, and authentication. It stops short of stating permission requirements or what the response confirms, which is the only remaining gap.

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 the baseline would be 3, but the schema descriptions are bare ranges ("1-60", "0-168", "0-50"). The description supplies the business meaning that those labels lack, explicitly mapping each numeric field to its policy effect, which is real added value.

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 ("Sets") and then enumerates the exact three settings affected: free-cancellation window, bookings on an unpaid pack, and days-ahead booking limit. That enumeration makes the scope unmistakably distinct from siblings such as set_stay_rules or set_opening_hours without needing to name them.

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: the tool configures booking policy for a single venue. The description never names an alternative tool or a when-not-to-use condition, so the agent must infer that other set_* tools cover different configuration domains.

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