Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

ticketmaster_discover_city_events

Read-only

Fetch a zero-based page of Ticketmaster events for one discover-city slug. Use ticketmaster_discover_cities to obtain slugs, ticketmaster_discover_category_events for category browsing, or ticketmaster_venue_events for one venue's calendar.

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": {
      "city": "<city>"
    },
    "name": "ticketmaster_discover_city_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesRequired. City slug returned by ticketmaster_discover_cities.
pageNoOptional. Zero-based event page, 0-49. Defaults to 0.
countryNoOptional. Two-letter country code matching the selected city. Defaults to US.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the pagination nuance ('zero-based page'), which is useful context, but discloses nothing about rate limits, result ordering, or what happens at page boundaries. With annotations carrying the behavioral load, a 3 is appropriate.

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?

Two sentences with zero waste: the first defines the operation and its scope, the second handles disambiguation. The core purpose is front-loaded before the routing guidance.

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 explained, and annotations cover the safety profile. The description supplies the routing an agent needs to pick this tool correctly; only minor behavioral details (ordering, page limits) are absent, which the schema partly covers.

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%, so the schema already documents city, page, and country with their defaults and constraints. The description restates that events are for a 'discover-city slug', reinforcing the slug dependency but adding no syntax or format detail beyond the schema. Baseline 3 is correct.

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 (Fetch), resource (Ticketmaster events), and scope (one discover-city slug, zero-based page). It explicitly differentiates itself from three siblings by naming them, so an agent can identify the correct tool 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: use ticketmaster_discover_cities to get slugs, ticketmaster_discover_category_events for category browsing, and ticketmaster_venue_events for a venue's calendar. This is a clear when-to-use-this-vs-alternatives statement with no inference required.

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

All Crawlora MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources