Crawlora MCP

ticketmaster_attraction_related

Read-only

Fetch the Fans Also Viewed attractions from one Ticketmaster attraction page; an attraction without recommendation data returns an empty list. Use ticketmaster_attraction to look up an attraction, or ticketmaster_attraction_events for its event listings.

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_attraction_related"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required. Numeric Ticketmaster attraction id.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, openWorldHint), so the bar is lower, and the description still adds a genuinely useful behavioral trait: a page lacking recommendation data returns an empty list rather than erroring. It does not mention any auth or rate-limit behavior, but the key edge case is disclosed.

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, both load-bearing, with the core purpose front-loaded and the sibling routing following. Zero filler.

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?

An output schema exists so return values need no explanation, and the description covers the one non-obvious outcome (empty list on missing recommendations) plus sibling routing. Nothing an agent needs to call this correctly is missing.

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 description coverage is 100% and the single 'id' param is already documented as a required numeric Ticketmaster attraction id. The description references 'one Ticketmaster attraction page' but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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) and a precisely named resource (Fans Also Viewed attractions from one Ticketmaster attraction page), which no sibling covers. An agent can distinguish it from ticketmaster_attraction and ticketmaster_attraction_events 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 Guidelines4/5

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

Explicitly names the two adjacent siblings and their purposes ('use ticketmaster_attraction to look up an attraction, or ticketmaster_attraction_events for its event listings'), which implies this tool is for recommendation/related data once an id is known. It gives clear context but no explicit 'when not to use' exclusion.

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

All Crawlora MCP tools Inspect

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

Need Help?