Skip to main content
Glama

ÖLEN Music & Gastro Hall — table booking

ÖLEN — upcoming events / афиша

olen_list_events
Read-only

Upcoming live-music nights and special events at ÖLEN (Almaty) with local date/time, price and page URL. Use the slug in olen_book_table.event_slug. Афиша ÖLEN: «что сегодня в ÖLEN», «какие вечера на неделе».

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "olen_list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoLanguage of titles: ru (default), kk, en, zh

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description is not burdened with safety disclosure. The description adds useful return context by naming local date/time, price, and page URL, plus the booking-slug linkage, but it does not mention ordering, pagination, or result limits.

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 is front-loaded with the core purpose and is short overall. The Russian intent examples occupy a reasonable amount of space and reinforce likely user queries, though they partly restate the title's афиша framing.

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 simple one-optional-parameter listing tool with no output schema, the description covers the core purpose and some returned fields. It still leaves 'upcoming' undefined in terms of time window and does not mention pagination or how many events are returned, so completeness is adequate but not thorough.

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% and the single lang parameter is documented with its enum and default in the schema. The description adds no additional meaning about language behavior, so baseline 3 is appropriate when the schema already carries parameter semantics.

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?

The description states a specific resource and scope: upcoming live-music nights and special events at ÖLEN in Almaty, including date/time, price, and page URL. It ties the output to olen_book_table.event_slug, but does not explicitly differentiate itself from olen_venue_info or other siblings.

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?

The Russian example queries imply typical use cases such as 'what is on today at ÖLEN' and 'what evenings are on this week', and the booking slug note gives downstream context. However, it does not explicitly say when to use this tool instead of olen_venue_info, nor does it state any exclusions.

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