Skip to main content
Glama

Set up the public booking page

dosai_update_booking_page
Destructive

Create or change the booking page: services (name, minutes, price), schedule, text after booking. Bot books into Google Calendar: schedule_source "bot"; else "own" with hours, working days and a calendar shared with the bot's Google address. Several doctors or saunas with own calendars: resources, one per bot schedule; each service needs someone. Only passed fields change; services and resources replace their lists. To switch on: slug, service, schedule. Prepayment: owner, in the cabinet. Owner or admin.

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_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNodosai.pro/b/<slug>
aboutNo
titleNo
enabledNo
servicesNo
hours_endNo
resourcesNo[] = one schedule again.
days_aheadNo
project_idYesFrom dosai_list_projects.
calendar_idNo
hours_startNo
hours_sourceNobusiness = project working hours; own = hours below.
resource_anyNofalse = no "any" option.
step_minutesNo
success_noteNo
working_daysNo0 = Sunday.
break_minutesNo
resource_pickNofalse = always "any".
resource_firstNoCities, branches: who (where) first, then its services.
resource_labelNo
resource_any_byNoorder = list order.
schedule_sourceNo
end_is_last_startNo
min_notice_minutesNo
resource_label_customNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / resource_any
      Added value: +{
      +  "description": "false = no \"any\" option.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / resource_any_by
      Added value: +{
      +  "description": "order = list order.",
      +  "enum": [
      +    "load",
      +    "order"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / resource_first
      Added value: +{
      +  "description": "Cities, branches: who (where) first, then its services.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / resource_label_custom
      Added value: +{
      +  "maxLength": 40,
      +  "type": "string"
      +}
    • addedInput schema / properties / resource_pick
      Added value: +{
      +  "description": "false = always \"any\".",
      +  "type": "boolean"
      +}
  2. Changed9 schema fields changed
    • removedInput schema / properties / end_is_last_start / description
      Removed value: -"true = hours_end is the last possible start, not closing time."
    • changedInput schema / properties / hours_source / description
      Previous value: -"business = the project's working hours; own = hours_start and hours_end below."New value: +"business = project working hours; own = hours below."
    • addedInput schema / properties / resource_label
      Added value: +{
      +  "enum": [
      +    "doctor",
      +    "master",
      +    "sauna",
      +    "branch",
      +    "custom"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / resources
      Added value: +{
      +  "description": "[] = one schedule again.",
      +  "items": {
      +    "additionalProperties": false,
      +    "properties": {
      +      "caption": {
      +        "type": "string"
      +      },
      +      "function": {
      +        "description": "A bot_schedules function_id or name.",
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "services": {
      +        "description": "Its service ids or names.",
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      }
      +    },
      +    "required": [
      +      "name",
      +      "function",
      +      "services"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 20,
      +  "type": "array"
      +}
    • removedInput schema / properties / schedule_source / description
      Removed value: -"bot = the bot's calendar function schedule; own = the fields below."
    • changedInput schema / properties / services / items / properties / id / description
      Previous value: -"Keep the id of an existing service; omit for a new one."New value: +"Existing id; omit for new."
    • changedInput schema / properties / slug / description
      Previous value: -"Page address: dosai.pro/b/<slug>."New value: +"dosai.pro/b/<slug>"
    • removedInput schema / properties / success_note / description
      Removed value: -"What the client reads after booking: address, how to get there."
    • changedInput schema / properties / working_days / description
      Previous value: -"0 = Sunday ... 6 = Saturday."New value: +"0 = Sunday."
  3. Changed1 schema field changed
    • addedInput schema / properties / schedule_source
      Added value: +{
      +  "description": "bot = the bot's calendar function schedule; own = the fields below.",
      +  "enum": [
      +    "bot",
      +    "own"
      +  ],
      +  "type": "string"
      +}
  4. 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."
  5. 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)$"
  6. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare a non-read-only, destructive, open-world write. The description earns credit for explaining the destructive edge ('`services` and `resources` replace their lists') and the partial-update rule ('Only passed fields change'), plus an external dependency: a calendar must be shared with the bot's Google address. It does not state reversibility, failure modes, or that removed services/resources may break existing bookings.

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?

The tool's purpose and required activation fields are front-loaded, and the replace-vs-merge rule is called out instead of buried. The telegraphic fragments ('else "own" with hours', 'Prepayment: owner, in the cabinet') are compact for a 25-parameter tool, though a few are compressed to the point of ambiguity.

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, no-output-schema, 25-parameter write tool with limited schema coverage, the description covers the highest-risk semantics (list replacement, calendar sharing dependency, permissions) but leaves a third of the parameters uninterpreted. An agent could invoke it safely but could not confidently set the scheduling-timing parameters without falling back to the sparse schema.

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 only 36% across 25 parameters, so the description must carry weight. It explains services fields, the bot/own schedule_source branch, hours/working days, resource-per-schedule, and the enablement trio, but leaves a large undocumented set (step_minutes, break_minutes, min_notice_minutes, days_ahead, end_is_last_start, resource_first/pick/any/any_by, resource_label_custom, success_note) with no added meaning.

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?

Opens with a specific verb and resource ('Create or change the booking page') and enumerates the configurable surfaces (services with name/minutes/price, schedule, text after booking). This is clearly not the read-side sibling dosai_get_booking_page, and the scope (page setup, not bot settings) is distinguishable, though no sibling is named explicitly.

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 concrete activation prerequisites ('To switch on: slug, service, schedule') and an explicit out-of-scope pointer for prepayment ('owner, in the cabinet'), which tells the agent this tool won't do it. It also routes between schedule_source modes. It stops short of naming alternative tools for the adjacent settings, so not a 5.

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