Skip to main content
Glama

ÖLEN Music & Gastro Hall — table booking

ÖLEN — venue info / о заведении

olen_venue_info
Read-only

Address, opening hours, phone/WhatsApp, menus, rooms, banquet and New Year 2027 corporate prices of ÖLEN Music & Gastro Hall (Almaty). Адрес, часы, контакты, меню, залы, банкеты и корпоративы Ö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_venue_info"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 safety and locality are covered and the description only needs to add scope. It does add scope by naming the specific data categories, including time-sensitive New Year 2027 corporate pricing, but says nothing about response shape, language of returned content, or freshness of prices.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The content list is front-loaded and easy to scan, but the entire description is duplicated verbatim in Russian, roughly doubling length for an audience that may only need one language. A shorter bilingual note or a single-language list would carry the same 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?

For a zero-parameter, read-only info tool with no output schema, the description does the essential job of telling the agent which data categories come back, which is exactly what is missing from structured fields. Only freshness of hours/prices and content language remain unstated, which are minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline is 4 and the empty schema leaves nothing for the description to clarify. No parameter-level ambiguity exists.

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 enumerates concrete resources the tool returns — address, hours, phone/WhatsApp, menus, rooms, banquet and New Year 2027 corporate prices — for a named venue, so an agent immediately knows this is the static-information endpoint. It distinguishes itself in practice from olen_book_table and olen_list_events by being purely informational, though it never names those siblings explicitly.

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?

Usage is implied by the content list: fetch this when a user asks about location, hours, contacts, menus, halls or banquet pricing. There is no explicit when-to-use statement, no exclusion such as 'do not use this to check an existing reservation', and no mention of the booking siblings, so routing is left to inference.

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