Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

ticketweb_search

Read-only

Search TicketWeb events by artist, event, or venue using a 2–200 character query. Results include each event name, canonical URL, local venue start time, and ticket availability (in_stock, sold_out, or unknown when TicketWeb reports no state). Empty results are valid; use the returned event URL with ticketweb_event for ticket pricing, which is not present in search results.

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": {
      "q": "<q>"
    },
    "name": "ticketweb_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesRequired. Artist, event, or venue query.
pageNoOptional. One-based result page, 1-50. Defaults to 1.

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.5/5.0
Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuine context beyond them: the shape of each result, the ticket-availability enum values including the 'unknown' case, and the fact that pricing is deliberately absent. It doesn't describe pagination limits or rate behavior, but for a read-only search that is minor.

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?

Three front-loaded sentences with no filler: purpose first, result contents second, routing/edge-case last. Every clause carries information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers purpose, result shape, the availability enum, the empty-result case, and the handoff to ticketweb_event. With an output schema present, return-value documentation is a bonus rather than a requirement, so nothing material 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 coverage is 100%, so the baseline is 3, but the description adds a real constraint the schema omits: the query must be 2–200 characters. The page parameter is left entirely to the schema, which is acceptable given its full description.

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 (search TicketWeb events) and names the three query dimensions (artist, event, venue). It also implicitly separates itself from ticketweb_event by declaring that pricing is NOT in search results.

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 clear routing: use the returned event URL with ticketweb_event for pricing, and notes that empty results are valid rather than an error. It does not address when to prefer this over sibling event-search tools like ticketmaster_search_events, so it stops short of explicit when-not guidance.

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