Skip to main content
Glama

Check the iiko key really works

dosai_check_iiko_connection

Ask iiko with the restaurant's API key and return what it sees: organisations, terminal groups (halls) and whether table reservations are available. Pass api_key to check a key BEFORE saving it, or omit it to check the saved one. Saving a key with dosai_update_booking_system does not check it. 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>"
    },
    "name": "dosai_check_iiko_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoOmit to check the saved key.
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

A4.3/5.0
Behavior4/5

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

Annotations cover only title and the safety flags; the description adds real context beyond them — the editor-role prerequisite, the fact that a key write via dosai_update_booking_system performs no verification, and the shape of the observed result. Minor tension with readOnlyHint=false, since the tool reads from an external system, but the outbound call plausibly explains the non-read-only flag, so it is not a contradiction.

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?

Three tight sentences, front-loaded with what the tool returns before the operational rules. No filler, though the return list and the save/check distinction could be ordered even more crisply for a scanning agent.

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?

With only two parameters, no output schema and no nested objects, the definition supplies nearly everything needed: what is returned, how api_key toggles between pre-save validation and saved-key validation, and the role requirement. Only the failure-mode behavior for an invalid key is left implicit.

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 100%, with api_key already documented as 'Omit to check the saved key', so the description largely repeats the schema for that parameter. Its only addition is the 'check before saving' framing, which is useful but marginal; baseline 3 is appropriate.

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?

States a specific verb and resource — ask iiko with the restaurant's API key — and enumerates what comes back: organisations, terminal groups (halls) and reservation availability. This makes it unmistakably distinct from the mutation sibling dosai_update_booking_system and from the other check_* tools.

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

Usage Guidelines5/5

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

Explicitly prescribes both modes of use: pass api_key to validate a key BEFORE saving it, omit it to validate the saved one. It also names the sibling that saves keys and warns that saving does not validate, which is exactly the decision point an agent needs.

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