Skip to main content
Glama

Change the booking rules

set_stay_rules

Check-in and check-out times, whether online bookings are confirmed at once or wait for the venue, and until how many days before arrival a guest may cancel. Only the fields sent are changed. 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_stay_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesThe venue’s address name, the "name" in name.bookare.app.
access_keyYesThe venue’s access key.
check_out_byNoHH:MM
check_in_fromNoHH:MM
instant_confirmationNoFalse = each online booking waits for the venue to confirm.
guest_can_cancel_until_days_beforeNo0-60

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent mutation, so the safety bar is partially covered. The description does add genuinely useful behavior beyond that: "Only the fields sent are changed" discloses partial-update semantics, which matters given idempotentHint=false. It does not disclose permission requirements, whether changes affect existing bookings, or what happens on invalid time values.

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 with no filler, and the enumerable settings are front-loaded before the scoping rules. The opening is a bare noun-phrase fragment rather than a statement of action, which slightly weakens the lead.

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 six-parameter mutation tool with no output schema, the description covers scope and partial-update behavior but omits error handling, permission needs, and any return-value expectation. Adequate, but an agent still has open questions before calling it.

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 the baseline is 3. The description restates the meaning of instant_confirmation ("whether online bookings are confirmed at once or wait for the venue") and the cancellation parameter, but the schema already conveys both, so it adds little beyond the structured fields.

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 names the specific settings it governs (check-in/check-out times, instant confirmation, cancellation window) and the scope (one venue identified by address and access key), so the resource is clear. However, it never states a verb like "sets" or "changes," and it offers no differentiation from the sibling set_booking_rules, leaving an agent to guess which of the two applies.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no exclusion of alternatives; the near-identical sibling set_booking_rules is not mentioned at all. The only contextual hint is the scoping line "Acts on one venue, given its address and access key," which tells the agent nothing about choosing this tool over its sibling.

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