Crawlora MCP

ticketmaster_suggest

Read-only

Returns autocomplete suggestions for a partial query. q: Required. Partial artist, event, team, or venue query. Use ticketmaster_search_events to search Ticketmaster events.

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": "ticketmaster_suggest"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Required. Partial artist, event, team, or venue query.

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 7, 2026

TDQS

A3.9/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 carried by structured data. The description adds the autocomplete/typeahead behavior, but says nothing about result format, limits, or rate behavior. With annotations covering the basics, 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core behavior, with the alternative named last. The only redundancy is restating the 'q' definition already present in the schema.

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-parameter read-only lookup tool with an output schema present, the description covers what an agent needs to call it correctly and when to prefer the search sibling. Nothing critical is missing, though it could say more about how the partial query behaves.

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 parameter 'q' is fully documented in the schema. The description merely restates the same definition ('Partial artist, event, team, or venue query'), adding no syntax or formatting detail beyond the schema. 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+resource: 'Returns autocomplete suggestions for a partial query.' This clearly distinguishes it from search-oriented siblings like ticketmaster_search_events, and it also enumerates the entity types covered (artist, event, team, venue).

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?

It explicitly routes the agent to ticketmaster_search_events for full event search, which clarifies the boundary between autocomplete and search. It stops short of stating an explicit 'when not to use this tool' rule or other alternatives, so it falls just below the top bar.

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.