Skip to main content
Glama

Booking confirmations and reminders

dosai_update_booking_settings
Destructive

Switch on and tune what a booked client receives: a confirmation right after booking and up to 5 reminders before the visit (e.g. 1440 and 120 minutes). Only what you pass changes; reminders replaces the whole list. Texts go to REAL clients, show them to the owner first; an empty text means the platform's standard wording. Current values: dosai_get_booking_settings. Requires editor role.

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": {
      "project_id": "<project_id>"
    },
    "name": "dosai_update_booking_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
enabledNoMaster switch for booking messages.
templateNoCommon reminder text.
remindersNo
project_idYesFrom dosai_list_projects.
confirmation_textNo
confirmation_enabledNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description usefully sharpens that into concrete semantics ('Only what you pass changes; reminders replaces the whole list') and flags real-client impact, editor role, and empty-text fallback. It still doesn't say what the response contains or what happens to confirmation_text when confirmation_enabled is false, so the added value is real but partial.

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?

Dense but front-loaded: effect first, then mutation semantics, then the client-facing warning, cross-reference and role. The final sentence packs three unrelated items (real clients, empty-text fallback, role) which slightly blurs the hierarchy, but nothing is redundant.

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 destructive settings mutation with no output schema, it covers the essentials: partial-update semantics, list replacement, role requirement, and the read counterpart. It omits return shape and edge cases such as disabling confirmation while leaving text set, so an agent can call it but cannot fully predict the outcome.

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?

Against 50% schema coverage it adds genuine meaning: reminders is replace-not-merge with a cap of 5, offsets are minutes before the visit with worked examples (1440, 120), and an empty text falls back to platform wording. It does not distinguish enabled from confirmation_enabled or clarify the interaction between template and per-reminder text, leaving some params to the schema alone.

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 and resource ('Switch on and tune what a booked client receives') and enumerates exactly what is configurable: a confirmation right after booking plus up to 5 reminders before the visit. That scope separates it cleanly from the sibling page/system settings tools without needing their schemas.

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?

Gives the read-before-write path explicitly ('Current values: dosai_get_booking_settings') and the access prerequisite ('Requires editor role'), plus a real-world caution to show texts to the owner first. It never states when not to use it or how it differs from dosai_update_booking_page / dosai_update_booking_system, so it stops short of full routing guidance.

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