Skip to main content
Glama

biletix_list_by_category

Retrieve featured Biletix events by category slug from homepage listings, with an optional 1–50 limit and a list of categories available today.

Instructions

Featured events in one category, from the homepage's SSR listings. category: the URL-slug prefix, e.g. "music" (concerts). limit 1..50. Returns events in that category plus the list of categories present on the homepage today (when the homepage is music-heavy, other categories may be empty — the site renders non-music categories 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": {
      "category": "<category>"
    },
    "name": "biletix_list_by_category"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
categoryYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations at all, the description carries the full load and does disclose non-obvious behavior: results come from server-side-rendered homepage listings, and the site renders non-music categories client-side, so other categories may legitimately return empty. That empty-result caveat is exactly the kind of thing an agent would otherwise misinterpret as an error. It does not cover rate limits, auth, or pagination, keeping it below a 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?

The purpose is front-loaded in the first clause, followed by parameter hints and then the rendering caveat, so the important information arrives early. It is compact with no filler, though the parenthetical caveat is dense and could be split for easier scanning.

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?

An output schema exists, so return values need only be sketched, and the description still notes that it returns both the events and the homepage's present categories. Combined with the parameter semantics and the SSR/client-side caveat, an agent has enough to call and interpret this tool; only explicit sibling routing is missing.

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 description coverage is 0%, so the description must compensate, and it does for both parameters: category is explained as the URL-slug prefix with a concrete example ("music" for concerts), and limit is bounded to 1..50. It omits the default value of 10 present in the schema, which is a minor gap rather than a serious one.

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?

States a specific verb and resource ("Featured events in one category") and pins the data source ("homepage's SSR listings"), which meaningfully separates it from search/trending siblings. It stops short of naming an alternative tool explicitly, so an agent still has to infer the boundary against biletix_trending and biletix_search_events.

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 description gives operational context (category is a URL-slug prefix, limit is 1..50) and a usage-relevant caveat that non-music categories may render empty, which helps an agent interpret results. However, there is no explicit when-to-use/when-not guidance relative to the five sibling tools, so selection is only implied by the 'featured/homepage' framing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.