Skip to main content
Glama

Create or update a booking

dosai_upsert_booking
Destructive

Record a booking made outside the assistant so the platform confirms it and reminds the client. Same external_id again = update; a new start_at = reschedule; status "cancelled" = cancel. start_at without an offset is project local time. The answer says whether the client's WhatsApp is a known contact (only known contacts get messages).

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>",
      "external_id": "<external_id>",
      "start_at": "<start_at>"
    },
    "name": "dosai_upsert_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNoClient's WhatsApp number, e.g. +77011234567. Or pass conversation_id.
statusNo
confirmNofalse = do not send the confirmation message.
serviceNo
start_atYesISO 8601, or 2026-09-23 15:00 in the project's time zone.
project_idYesFrom dosai_list_projects.
client_nameNo
external_idYes
conversation_idNoFrom dosai_list_conversations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / conversation_id / description
      Previous value: -"Conversation id, as returned by dosai_list_conversations."New value: +"From dosai_list_conversations."
  2. 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."
  3. Changed2 schema fields changed
    • removedInput schema / properties / conversation_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)$"
    • 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)$"
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), it discloses real behavioral consequences: the platform sends a confirmation and reminder, and the response reveals whether the client's WhatsApp is a known contact because only known contacts receive messages. What it does not disclose is what happens to fields omitted on an update (e.g., whether service or client_name are cleared), which matters for a destructive write.

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?

Three dense sentences, each earning its place: what it does, how the upsert keys map to update/reschedule/cancel, and the timezone rule plus return-value hint. The operation-mapping sentence is front-loaded before the edge-case details, so the most decision-relevant content comes first.

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?

For a 9-parameter destructive write with no output schema, the description covers the core flow, the identity semantics, the timezone rule, and a return-value hint, which is close to sufficient. It falls short on update-merge behavior for omitted fields and on any prerequisite about the contact existing before a message can be sent.

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?

Schema coverage is 56%, and the description adds genuine meaning to key parameters: external_id is the upsert identity, start_at without an offset means project-local time, and status='cancelled' is the cancellation path. It says nothing about phone vs conversation_id, confirm, service, or client_name, leaving roughly half the parameters 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?

The description names a specific verb and resource ('Record a booking') and scopes it to bookings made outside the assistant, which separates it from the booking page/settings/system tools in the sibling list. It also explains the upsert key semantics (same external_id = update, new start_at = reschedule, status 'cancelled' = cancel), so an agent knows exactly which operation it is invoking.

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?

It gives a clear trigger condition: use this when a booking was made outside the assistant and needs platform confirmation and client reminders. It does not state exclusions or point to alternatives, notably the sibling dosai_cancel_booking, even though it describes status='cancelled' as a cancel path — a mild routing ambiguity left unresolved.

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