Skip to main content
Glama

FavCRM

by io.favcrm

update_booking_settings

Idempotent

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
showCouponNoShow coupon field in booking flow
calendarStyleNoBooking flow calendar presentation
showAccessPassNoShow access pass/package options in booking flow
cooldownMessageNoOptional message shown when cooldown blocks a booking
blockUntilFinishedNoBlock customers from booking again while they have active bookings
globalCooldownDaysNoMinimum days between customer bookings, or null to disable
accessPassAfterMinutesNoMinutes after booking end when the access QR remains usable
bookingReminderEnabledNoSend the default pre-booking reminder
memberReschedulingModeNoChoose whether rescheduling is disabled, merchant-only, or available to members
sameDayReminderEnabledNoSend an additional same-day reminder before booking start
accessPassBeforeMinutesNoMinutes before booking start when the access QR becomes usable
allowMemberCancellationNoAllow members to cancel bookings from the customer portal
bookingReminderLeadHoursNoHours before booking start for the default reminder
hideUnavailableTimeslotsNoHide unavailable timeslots instead of showing them as full
sameDayReminderLeadHoursNoHours before booking start for the same-day reminder
requireBookingConfirmationNoRequire merchant confirmation before bookings are confirmed
minimumAdvanceBookingMinutesNoMinutes before slot start when customer booking closes. null/0 = no cutoff; set > 0 to require advance notice
memberCancellationCutoffHoursNoHours before booking start when member cancellation closes, or null for no cutoff

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesTool result payload — shape varies per tool, see the tool description
summaryYesOne-line human-readable summary of the action
renderTypeYesUI rendering hint for the result

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed2 schema fields changed
    • 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"
+}
  2. Changed1 schema field changed
    • 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"
+}
  3. Changed1 schema field changed
    • 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"
  4. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds the partial update pattern, which informs the agent that repeated calls with the same fields produce the same result (consistent with idempotency). No contradictions, and the description adds value beyond annotations.

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 sentences, zero wasted words. The purpose and usage pattern are front-loaded. Every sentence earns its place.

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?

Given the high parameter count (18) and presence of an output schema, the description is minimal. It does not explain what 'global booking settings' entail, that these settings apply company-wide, or that a prior read via get_booking_settings is recommended. The description is adequate but leaves gaps for an agent to use it effectively without additional context.

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% (all 18 parameters have detailed descriptions). The tool description does not add any parameter-specific information. Baseline 3 is appropriate as the schema does the heavy lifting.

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?

The description clearly states the verb 'Update' and the resource 'global booking settings'. This distinguishes it from sibling tools like get_booking_settings (read) and others. The scope is precise and unambiguous.

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?

The description implicitly guides when to use the tool (when changing settings) and the partial update pattern ('Pass only the fields you want to change'). However, it does not explicitly mention that get_booking_settings is the appropriate sibling for reading current settings or when not to use this tool. The guidance is clear but lacks exclusions.

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

All FavCRM toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.3/5.0
Disambiguation2/5

Many tools have overlapping boundaries, such as generate_post_cover/attach_post_cover_from_job/upload_post_cover_from_url, update_deal/update_deal_stage/mark_deal_won/mark_deal_lost, and booking status transitions (confirm/cancel/complete/mark_no_show). The catch-all execute_tool adds further ambiguity.

Naming Consistency4/5

Nearly all tools follow a consistent verb_noun snake_case convention (create_*, list_*, get_*, update_*, delete_*, restore_*). Minor exceptions like 'clone' and 'execute_tool' are still readable and do not significantly break the pattern.

Tool Count1/5

With 223 tools, the server is extremely over-scoped. Even for a full CRM platform, this many tools overwhelms context windows and makes tool selection impractical. It far exceeds the reasonable range for an MCP server.

Completeness3/5

The surface is broad but has notable gaps: no update_booking/delete_booking, no delete_product, no send_message/send_campaign (referenced but absent), and no delete_staff/resource. Some workflows dead-end or require manual approval steps.

Resources