Skip to main content
Glama

biletix_list_venues

Lists distinct venues behind Biletix homepage featured events, with city and featured-event count (limit 1-50). Use it to identify venues, then fetch each venue's page URL and upcoming events.

Instructions

Venues behind the homepage's featured events: distinct venue names with city and featured-event count. limit 1..50. Use biletix_get_event to get a venue's page URL, then biletix_venue_events for its upcoming events.

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": "biletix_list_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and discloses the critical behavioral fact that results are limited to venues tied to featured homepage events, not a full venue directory. It also names the returned fields and the 1..50 bound, though it says nothing about ordering, pagination beyond limit, or empty-result behavior.

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?

Three short sentences, front-loaded with scope, then the numeric bound, then the chaining advice; no filler. The colon-led first clause is slightly clipped but still readable.

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 not be spelled out, and the description still names the key fields for orientation. For a one-parameter, read-only listing tool with no annotations, the combination of scope, bounds and chaining covers what an agent needs, with only ordering and pagination left unspecified.

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% and the single 'limit' parameter has no description or bounds in the schema, so the description's 'limit 1..50' supplies meaning the schema does not. It does not state what the default of 20 means or what happens when more venues exist than the limit, leaving a small gap.

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?

The first sentence gives a specific verb (list), resource (venues) and a precise scope: venues behind the homepage's featured events, returning distinct venue names with city and featured-event count. That scope constraint is exactly what separates it from biletix_venue_events and biletix_get_event, so an agent can pick it without inspecting the 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?

It explicitly routes downstream work: use biletix_get_event for a venue's page URL, then biletix_venue_events for upcoming events, which defines this tool's place in a chain. It offers no exclusions against biletix_trending, biletix_search_events or biletix_list_by_category, so the alternative-selection guidance is incomplete rather than exhaustive.

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