FavCRM

update_booking_settings

Idempotent

Update global booking settings. Pass only the fields you want to change.

Input Schema

Name	Required	Description
`showCoupon`	No	Show coupon field in booking flow
`calendarStyle`	No	Booking flow calendar presentation
`showAccessPass`	No	Show access pass/package options in booking flow
`cooldownMessage`	No	Optional message shown when cooldown blocks a booking
`premisePassCode`	No	One premise pass code for this company. Guest templates show it only when they include the pass code variable. Empty clears it.
`blockUntilFinished`	No	Block customers from booking again while they have active bookings
`globalCooldownDays`	No	Minimum days between customer bookings, or null to disable
`accessPassAfterMinutes`	No	Minutes after booking end when the access QR remains usable
`bookingReminderEnabled`	No	Send the default pre-booking reminder
`memberReschedulingMode`	No	Choose whether rescheduling is disabled, merchant-only, or available to members
`sameDayReminderEnabled`	No	Send an additional same-day reminder before booking start
`accessPassBeforeMinutes`	No	Minutes before booking start when the access QR becomes usable
`allowMemberCancellation`	No	Allow members to cancel bookings from the customer portal
`bookingReminderLeadHours`	No	Hours before booking start for the default reminder
`hideUnavailableTimeslots`	No	Hide unavailable timeslots instead of showing them as full
`sameDayReminderLeadHours`	No	Hours before booking start for the same-day reminder
`requireBookingConfirmation`	No	Require merchant confirmation before bookings are confirmed
`bookingReminderLeadHoursList`	No	Up to four reminder leads in hours. Replaces the legacy pair when set. Empty turns customer reminders off. Leads must be at least 2 hours apart.
`minimumAdvanceBookingMinutes`	No	Minutes before slot start when customer booking closes. null/0 = no cutoff; set > 0 to require advance notice
`memberCancellationCutoffHours`	No	Hours before booking start when member cancellation closes, or null for no cutoff

Output Schema

Name	Required	Description
`data`	Yes	Tool result payload — shape varies per tool, see the tool description
`summary`	Yes	One-line human-readable summary of the action
`renderType`	Yes	UI rendering hint for the result

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

addedInput schema / properties / bookingReminderLeadHoursList

Added value: +{
+  "description": "Up to four reminder leads in hours. Replaces the legacy pair when set. Empty turns customer reminders off. Leads must be at least 2 hours apart.",
+  "items": {
+    "maximum": 168,
+    "minimum": 1,
+    "type": "integer"
+  },
+  "maxItems": 4,
+  "type": "array"
+}

addedInput schema / properties / premisePassCode

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 32,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "One premise pass code for this company. Guest templates show it only when they include the pass code variable. Empty clears it."
+}

Changed2 schema fields changedAug 18, 2026

addedInput schema / properties / accessPassAfterMinutes

Added value: +{
+  "description": "Minutes after booking end when the access QR remains usable",
+  "maximum": 1440,
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / accessPassBeforeMinutes

Added value: +{
+  "description": "Minutes before booking start when the access QR becomes usable",
+  "maximum": 1440,
+  "minimum": 0,
+  "type": "integer"
+}

Changed1 schema field changedAug 12, 2026

addedInput schema / properties / memberReschedulingMode

Added value: +{
+  "description": "Choose whether rescheduling is disabled, merchant-only, or available to members",
+  "enum": [
+    "disabled",
+    "merchant_only",
+    "member"
+  ],
+  "type": "string"
+}

Changed1 schema field changedJul 9, 2026

changedInput schema / properties / minimumAdvanceBookingMinutes / description

Previous value: -"Minutes before slot start when customer booking closes. null uses service duration; 0 disables cutoff"New value: +"Minutes before slot start when customer booking closes. null/0 = no cutoff; set > 0 to require advance notice"

First observedJun 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare non-readonly, idempotent, non-destructive, and closed-world behavior. The description adds that callers should send only changed fields, which implies untouched settings are preserved, but it does not explain scope beyond 'global', permissions, or effects on in-flight bookings.

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?

Two short sentences, front-loaded with the core action and followed by the key invocation rule. There is no filler or repetition.

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?

Given the rich schema with descriptions for all 20 parameters, an output schema, and annotations covering safety and idempotency, the description is largely sufficient. It could still do more to warn that these are company-wide booking-flow settings and to mention related read tools, but the essentials are present.

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?

With 100% schema description coverage across all 20 optional parameters, the schema already carries the parameter semantics. The description adds only a general patch-style instruction and no parameter-specific details, matching the baseline for high schema coverage.

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 states a specific verb and resource: 'Update global booking settings.' This clearly signals a company-wide settings mutation, but it does not explicitly distinguish it from siblings such as get_booking_settings or update_service_schedule, which is why it falls short of a 5.

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?

The phrase 'Pass only the fields you want to change' gives useful partial-update guidance, but there is no explicit when-to-use context, no mention of alternatives like get_booking_settings for reading current values, and no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All FavCRM tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.