Skip to main content
Glama

biletix_search_events

Search Biletix featured concerts, theatre, festivals, and sports by keyword and optional city, then return matching event details such as dates, venue, and prices.

Instructions

Keyword search over biletix.com's currently featured events (the homepage's SSR listings — concerts, theatre, festivals, sport). query: e.g. "Simge", "Dolu Kadehi Ters Tut", "caz"; city: e.g. "istanbul", "ankara", "izmir" (matches the event's city). limit 1..50. Returns matching events (title, start/end, date text, venue, city, price from in TRY, category, event URL). Note: this searches featured listings only, not the full catalogue — the site's own search page renders client-side.

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": {
      "query": "<query>"
    },
    "name": "biletix_search_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNo
limitNo
queryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations exist, so the description carries the full burden and largely meets it: it discloses the data source (SSR homepage listings), the hard limitation (featured only, not the catalogue), the limit range 1..50, and the returned fields including TRY pricing. It omits anything about request cost, rate limiting, or whether results are ordered — minor gaps for a read-only search.

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

Conciseness5/5

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

Purpose is front-loaded in the first clause, then parameters, then return shape, then the caveat — a clean descending-priority structure. Every sentence is load-bearing, including the closing note about the client-side search page.

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 three-parameter search with an output schema, the description covers source, scope, parameters, return fields and the key caveat, so an agent can call it correctly. It does not say what happens when limit truncates a larger result set, nor whether results are ranked, which is the remaining uncertainty.

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?

Schema coverage is 0%, so the description must supply all meaning and does: query is exemplified with real artist/genre strings, city is exemplified with three cities and tied to the event's own city field, and limit is bounded to 1..50 (the schema itself imposes no such bound). It does not clarify city matching case sensitivity or partial matching, keeping it below 5.

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 ('keyword search over biletix.com's currently featured events') and immediately bounds the scope to the homepage SSR listings across concerts, theatre, festivals and sport. That scope statement is enough to separate it from biletix_trending, biletix_list_by_category and biletix_get_event without opening any 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?

Gives concrete query and city examples plus an explicit when-not clause: 'this searches featured listings only, not the full catalogue — the site's own search page renders client-side.' It never names a sibling as the alternative, so the agent must infer the fallback, which keeps it 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.