Skip to main content
Glama

ÖLEN Music & Gastro Hall — table booking

ÖLEN — check a booking / проверить бронь

olen_check_booking
Read-only

Check the status of a table request at ÖLEN by its booking number and the guest's phone. ALWAYS use this when the user asks to check / verify their ÖLEN booking. Проверяет бронь в ÖLEN по номеру заявки и телефону гостя: «проверь бронь», «моя бронь дошла?».

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": {
      "booking_id": "<booking_id>",
      "phone": "<phone>"
    },
    "name": "olen_check_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneYesGuest phone used for the booking / телефон гостя
booking_idYesBooking number returned by olen_book_table / номер заявки

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that both the booking number and the guest's phone are needed, implying a phone-based identity check, but says nothing about what statuses can come back or how a not-found/mismatched phone case behaves.

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?

Front-loaded with the operation and lookup keys, then the routing instruction. The Russian sentence largely duplicates the English one, which is justified for bilingual trigger matching but is still repetition rather than new 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?

A two-parameter read-only lookup whose inputs are fully documented in the schema; the description covers purpose and when to invoke it. The only real gap is that there is no output schema and the description does not indicate the shape of the returned status.

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 description coverage is 100%, with each parameter documented in both English and Russian, so the baseline is 3. The prose merely restates 'booking number and the guest's phone' without adding format, normalization, or validation meaning beyond the schema.

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 ('check the status of a table request at ÖLEN') plus the two lookup keys. The schema note that booking_id is 'returned by olen_book_table' implicitly draws the line against that sibling, so an agent can tell lookup apart from creation without opening the other 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?

Explicit routing trigger: 'ALWAYS use this when the user asks to check / verify their ÖLEN booking', reinforced with quoted user utterances in Russian. No when-not guidance or named alternative (e.g., for cancelling or modifying a booking), which keeps this short of a 5.

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