Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

ticketmaster_venue

Read-only

Returns normalized details and visitor information for one Ticketmaster venue. id: Required. Numeric Ticketmaster venue id. Use ticketmaster_venue_enhanced_details to get a Ticketmaster venue's enhanced branding details.

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": {
      "id": "<id>"
    },
    "name": "ticketmaster_venue"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesRequired. Numeric Ticketmaster venue id.

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.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds that results are 'normalized' and include visitor information, but does not mention auth requirements, rate limits, or error behavior. Adds some value over structured fields, but modestly.

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 short sentences, front-loaded with purpose, then the parameter note, then the sibling routing. No filler or redundancy beyond the mild restatement of the id parameter.

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?

For a single-entity read tool with readOnly/openWorld annotations and an output schema, the description covers what the tool is and which sibling to use for richer data. Return-value detail is correctly omitted given the output schema, leaving little an agent must infer.

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 fully documented in the schema. The description repeats 'id: Required. Numeric Ticketmaster venue id.' without adding format, sourcing, or lookup guidance beyond what the schema already provides, so baseline 3 applies for a 1-parameter tool.

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 ('Returns normalized details and visitor information for one Ticketmaster venue') with clear scope ('one'). It names the closest sibling (ticketmaster_venue_enhanced_details) and the differentiating data it does not return, so an agent can distinguish it without opening 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?

Explicitly routes the agent to ticketmaster_venue_enhanced_details for branding details, giving a concrete alternative and condition. It lacks an explicit statement of the inverse condition (when to prefer this tool), though the purpose sentence implies it.

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