Skip to main content
Glama

Connect iiko or change booking system settings

dosai_update_booking_system
Destructive

system=iiko: save the restaurant's iiko API key (check it FIRST with dosai_check_iiko_connection: a wrong key is saved without an error and looks connected), then choose the organisation and terminal group from dosai_get_booking_system, set the reservation length and the buffer between reservations. system=salon: connect an Altegio branch: connect=true, platform=altegio, company_id = the number in the journal address app.alteg.io/timetable/; no install, no password. A refusal says what the owner must fix. Needs admin role. horizon_days: days ahead the bot books. Then dosai_add_booking_system_functions. The iiko key passes through this chat, warn the owner. 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_update_booking_system"
  }
}

Input Schema

NameRequiredDescriptionDefault
systemYes
api_keyNoiiko only.
connectNosalon only.
platformNosalon only.
company_idNosalon only.
project_idYesFrom dosai_list_projects.
horizon_daysNosalon only.
buffer_minutesNoiiko only.
organization_idNoiiko only.
terminal_group_idNoiiko only.
reserve_duration_minutesNoiiko only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / confirm_mode
      Removed value: -{
      -  "description": "salon only.",
      -  "enum": [
      -    "pending",
      -    "confirmed"
      -  ],
      -  "type": "string"
      -}
    • addedInput schema / properties / connect
      Added value: +{
      +  "description": "salon only.",
      +  "type": "boolean"
      +}
  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. Changed3 schema fields changed
    • removedInput schema / properties / organization_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)$"
    • removedInput schema / properties / terminal_group_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.3/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds real operational context beyond them: a wrong iiko key is saved silently and appears connected, the API key transits the chat and the owner must be warned, refusals describe what the owner must fix, and the salon path requires no install or password. What it does not disclose is the overwrite behaviour implied by destructiveHint — whether existing settings or a previously connected system are replaced when switching branches.

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 system=iiko / system=salon branch labels front-load the two modes and let an agent skip the irrelevant half, which is efficient for an 11-parameter tool. Some clauses are compressed to the point of terseness ('A refusal says what the owner must fix'), and the trailing role sentence duplicates and partially contradicts the earlier permission statement.

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 destructive, multi-branch, 11-parameter tool with no output schema, the definition covers the sequencing, the prerequisite tools, the value sources for foreign IDs, the silent-failure trap, and the security warning about the API key. Remaining gaps are the partial-update/overwrite behaviour and the unresolved role requirement, both of which an agent would want before invoking.

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?

With 91% schema coverage the baseline is already high, yet the description still adds meaning the schema lacks: company_id is decoded as the number in the journal address app.alteg.io/timetable/<number>, horizon_days is glossed as days ahead the bot books, and the organisation/terminal group values are pointed at their source tool. It does not explain partial-update semantics, i.e. what happens to optional fields left unset even though only project_id and system are required.

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 the resource and splits it into two explicit branches (system=iiko connects an iiko API key and configures organisation/terminal group/reservation length/buffer; system=salon connects an Altegio branch), which maps directly onto the system enum. Naming dosai_get_booking_system, dosai_check_iiko_connection and dosai_add_booking_system_functions makes it distinguishable from those siblings. An agent can tell what this tool does and does not do without opening the schema.

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 workflow is unusually explicit: check the iiko key FIRST with dosai_check_iiko_connection, pull organisation and terminal group from dosai_get_booking_system, then finish with dosai_add_booking_system_functions. Preconditions for the salon path are also stated (no install, no password). The one flaw is the closing role guidance, 'Needs admin role' in the iiko branch versus 'Requires editor role' at the end, which leaves the permission requirement ambiguous.

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