Skip to main content
Glama

tm_search_attractions

Read-onlyIdempotent

Search Ticketmaster for attractions and artists using keywords and classification filters to find relevant performers and events.

Instructions

Search for attractions/artists on Ticketmaster.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tm_search_attractions"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNo
keywordNo
classificationNameNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the description adds nothing on top of them—no mention of pagination, result limits, what an 'attraction' record contains, or the required api_key.

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?

A single front-loaded sentence with no filler; it is not padded, but its brevity comes at the cost of specification rather than efficiency.

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

Completeness2/5

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

With three undocumented parameters, no output schema, and a crowded sibling set of Ticketmaster/SeatGeek tools, the definition leaves too much for the agent to guess about filtering behavior and return shape.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the meaning of all three parameters, yet it explains none. 'keyword' and 'classificationName' are never distinguished (e.g., free-text search vs. category filter), and the api_key requirement is unmentioned.

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?

States a specific verb (Search) and resource (attractions/artists on Ticketmaster), and the parenthetical 'attractions/artists' clarifies an ambiguous domain term. It does not, however, distinguish this from sibling tools like tm_search_events or tm_search_venues.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this versus tm_search_events, tm_get_event, tm_search_venues, or the SeatGeek performer search. The agent must infer from the name alone that this searches performers rather than events.

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