Retrieve normalized details for one Ticketmaster artist, team, or other attraction using its numeric attraction ID.
Get a Ticketmaster attraction. Returns normalized details for one Ticketmaster artist, team, or other attraction.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric Ticketmaster attraction id |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the behavioral burden. It states it 'Returns normalized details,' which implies a read operation and hints at output structure, but it does not disclose failure conditions, permissions, rate limits, or what 'normalized' entails. 'Get' is a weak but acceptable signal for a read-only operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences and front-loaded with the core action. Every phrase adds value, including the explicit types of attractions and the 'normalized details' outcome, with no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple single-parameter lookup, the description is nearly complete: it identifies the resource, action, and high-level return type. The absence of annotations and output schema would benefit from slightly more detail about output contents or error handling, but the tool is simple enough that the description adequately covers it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already provides 100% coverage with 'id' described as 'Numeric Ticketmaster attraction id.' The description adds no new parameter semantics beyond clarifying that an attraction can be an artist, team, or other entity, which is already implicit in the resource name.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific action ('Get') on a specific resource ('Ticketmaster attraction') and defines attraction as an artist, team, or other attraction. This distinguishes it from sibling tools like ticketmaster_event and ticketmaster_venue, making the purpose unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when the agent needs details for a single attraction by ID, but it does not explicitly state when to use this tool versus alternatives. It offers no contrast with sibling tools such as ticketmaster_attraction_events or ticketmaster_search_events, and no exclusions or prerequisites are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.