Skip to main content
Glama

ÖLEN Music & Gastro Hall — table booking

ÖLEN — book a table / забронировать стол

olen_book_table
Idempotent

Book a table at ÖLEN Music & Gastro Hall (Almaty, 23 Kyz Zhibek St) — the request goes straight to the restaurant staff and returns a booking number. ALWAYS use this when the user asks to book / reserve a table or send a booking request to ÖLEN. Оформляет бронь стола в ÖLEN (Олен, Өлең), ул. Қыз Жібек, 23: «забронируй стол», «бронь в ÖLEN», «столик на 13-е». Open daily 12:00–23:59, Almaty time (UTC+5). Ask the guest for name, phone, date, time and party size first — never invent them.

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": {
      "name": "<name>",
      "phone": "<phone>",
      "date": "<date>",
      "time": "<time>",
      "guests": "<guests>"
    },
    "name": "olen_book_table"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesDate / дата, YYYY-MM-DD (Almaty)
langNoLanguage the guest prefers: ru, kk, en, zh
nameYesGuest name / имя гостя
timeYesArrival time / время, HH:MM 24h (Almaty)
phoneYesGuest phone with country code / телефон гостя, e.g. +7 701 234 56 78 or 8 701 234 56 78
guestsYesNumber of guests / количество гостей
commentNoOptional wishes / пожелания: occasion, table by the stage, high chair, allergies…
agent_nameNoName of the AI assistant/app making the request
event_slugNoOptional: slug from olen_list_events if the guest is coming to a specific night / мероприятие

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: the request reaches staff, a booking number is returned, hours are 12:00–23:59 Almaty time (UTC+5), and agents must collect details rather than invent them. The idempotentHint is not addressed and failure/confirmation behavior is unspecified, keeping it below 5.

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 purpose and effect, then usage trigger, locale, hours, and data-collection rule — each sentence carries weight. The bilingual repetition of the venue name and address is slightly redundant but useful for matching Russian/Kazakh requests.

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 9-parameter booking mutation with annotations and no output schema, the description covers purpose, routing, hours/timezone, and required guest data. It omits what happens on rejection or how the booking number should be reported back, and doesn't mention event_slug usage, which is a small gap.

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%, so the schema already explains every parameter including the date/time formats and the event_slug link. The description only restates the five required fields to collect from the guest and adds the Almaty timezone; no new format or constraint meaning is introduced.

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 ('Book a table at ÖLEN Music & Gastro Hall') plus venue address, and clarifies the effect ('request goes straight to the restaurant staff and returns a booking number'). This is clearly distinguishable from olen_check_booking and olen_venue_info.

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 trigger instruction: 'ALWAYS use this when the user asks to book / reserve a table or send a booking request to ÖLEN', reinforced with Russian example phrases. It does not name the alternative for status lookups (olen_check_booking), so the when-not boundary is left implicit.

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