Skip to main content
Glama

Give the bot the functions of iiko, Altegio or YCLIENTS

dosai_add_booking_system_functions
Destructive

Create the bot's functions for the connected booking system in one go: find free time, book, show, move and cancel a booking (salon), or check tables, reserve, find a reservation and the stop list (iiko). Only missing ones are added. For a salon, disable_other=true switches off other booking functions (Google Calendar) so the bot does not book in two places. 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>",
      "system": "<system>"
    },
    "name": "dosai_add_booking_system_functions"
  }
}

Input Schema

NameRequiredDescriptionDefault
systemYes
project_idYesFrom dosai_list_projects.
disable_otherNo

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.6/5.0
Behavior5/5

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

With destructiveHint=true already declared, the description still adds substantive behavior: it discloses the add-only-if-missing semantics, warns that disable_other=true switches off other booking functions so the bot does not double-book, and states the editor-role auth requirement. Those are the exact side effects an agent needs before invoking a destructive batch operation.

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 with zero filler: the capability list comes first, then the per-system breakdown, then the disable_other caveat and auth requirement. Every clause carries operational information.

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 batch-provisioning tool with three parameters and no output schema, the description covers what gets created, per-system differences, idempotency, the destructive disable_other behavior, and the permission requirement. It omits what the caller sees on return (which functions were added vs. skipped) and what happens if the system is not yet connected — minor but real gaps.

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 only 33%, so the description must compensate — and it does for the two parameters that matter: it explains what each system value provisions and fully spells out the effect of disable_other, which the schema leaves as a bare boolean. project_id is only partly covered (the schema itself points to dosai_list_projects), which is the one small gap.

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 opens with a specific verb+resource ("Create the bot's functions for the connected booking system") and then enumerates exactly which functions are provisioned per system type (free time/book/show/move/cancel for salon; tables/reserve/find reservation/stop list for iiko). That enumeration distinguishes it cleanly from siblings like dosai_get_booking_system and dosai_update_booking_system, which read or modify settings rather than provisioning functions.

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 clear context for use: the target system must already be connected, an editor role is required, and "Only missing ones are added" sets the idempotent precondition. It also explains the disable_other branch for salons. It does not explicitly name an alternative tool (e.g. dosai_update_booking_system) or state a when-not-to-use condition, 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