Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

ticketweb_event

Fetches details for a TicketWeb event: venue, dates, age restriction, delivery methods, and ticket pricing. Reports no purchasable sections for free, sold-out, or access-code-gated events.

Instructions

Get a TicketWeb event. Returns details for one TicketWeb event: venue, dates, age restriction, delivery methods, and per-tier ticket pricing (base price, fee breakdown, and total) when tickets are on sale. has_tickets is false and sections is empty for a free/RSVP event with no paid tickets, a sold-out event, or an access-code-gated event -- TicketWeb's own data does not reliably distinguish these three cases at this level, so the response reports the shared observable state (no purchasable sections) rather than guessing which applies.

Input Schema

NameRequiredDescriptionDefault
idYesNumeric TicketWeb event id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers a genuinely useful disclosure: it explains what has_tickets=false plus empty sections actually means and that TicketWeb cannot distinguish free/RSVP, sold-out, and access-code-gated events at this level. That is valuable behavior not derivable from the schema. It does not cover error behavior or required permissions, keeping it short of 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 definition is front-loaded with the core action and payload, then the edge-case semantics. The second sentence is long but each clause earns its place by clarifying ambiguous return states.

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?

There is no output schema and no annotations, so the description must describe the response, and it does so substantively (fields returned plus the meaning of empty sections). Missing only error/permission context to reach a 5.

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% and the single id parameter is already documented as a numeric TicketWeb event id, so the description adds nothing beyond the structured field. Baseline 3 applies.

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 states a specific verb and resource ('Get a TicketWeb event') and enumerates the payload (venue, dates, age restriction, delivery methods, pricing). It is clear what it does, but it does not name or distinguish itself from siblings like ticketweb_search or ticketweb_venue.

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: fetch one event by id. There is no explicit when-to-use guidance, no statement of when-not to use it, and no routing to ticketweb_search for discovery or ticketweb_venue for venue-level lookups.

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

Deploy Server

Other Tools