Skip to main content
Glama

iiko, Altegio or YCLIENTS connection

dosai_get_booking_system
Read-onlyIdempotent

State of the booking system connected to the project, without secrets. system=iiko (restaurants): is the key saved, the organisation, halls, reservation settings, which bot functions exist. system=salon (Altegio): the connected branch, staff and services, bot functions.

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

Input Schema

NameRequiredDescriptionDefault
systemYes
project_idYesFrom dosai_list_projects.

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

A3.6/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint and destructiveHint already declared, the description still contributes meaningfully: 'without secrets' tells the agent that credentials are redacted, which matters for downstream reasoning and prevents it from assuming a token can be read. The per-system field enumeration also sets expectations for the response shape, though error/empty-state behavior is not disclosed.

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 description opens with the core definition and then uses parallel colon-lists for each system value, which is easy to scan. The trailing 'bot functions' phrase is repeated in both branches and could be factored out, but overall there is little waste.

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 two-parameter read tool with no output schema, listing the returned fields per system is the right move and largely covers the gap. However, the title advertises a YCLIENTS option that no enum value or description branch supports, and there is no indication of what happens when nothing is connected.

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 coverage is only 50%: project_id is documented in the schema ('From dosai_list_projects') but system is an unexplained enum. The description compensates partially by mapping each enum value to system type and to the specific fields returned, but says nothing about project_id or failure behavior for a project with no connected system.

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?

States a specific resource and verb: returns the connected booking system's state. It also distinguishes the two supported variants by naming what each system returns (iiko: key saved, organisation, halls, reservation settings; salon: branch, staff, services). It does not name sibling tools to rule out, and the title's mention of 'YCLIENTS' is never reflected in the description or enum, leaving a small ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implicit guidance exists: the system enum is mapped to business types ('iiko (restaurants)', 'salon (Altegio)'), which helps the agent choose the value. But there is no explicit when-to-use/when-not guidance and no reference to alternatives such as dosai_check_iiko_connection or dosai_get_booking_settings, so the agent must infer which read tool to pick.

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