Event Images
event_imagesRead-onlyIdempotent
Images for an event.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Ticketmaster
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds no behavioral context beyond what the annotations already convey. It doesn't explain how images are returned, whether the event ID must exist, or any additional operational traits. The annotations cover the safety profile, but the description itself is silent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely short, but it is under-specified rather than concise. It merely restates the title, so the sentence does not earn its place. No useful information is packed into the brevity.
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?
For a tool with a single generic 'id' parameter and no schema description, the description is insufficiently complete. It doesn't explain the nature of the images, the relationship to the event, or the return structure. An output schema exists, but the description still leaves the tool's purpose ambiguous.
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?
With schema coverage at 0%, the description carries the burden of explaining the 'id' parameter. The phrase 'Images for an event' implies that the id refers to an event, but it doesn't explicitly state that the parameter is an event identifier or describe the expected format. This provides marginal value over the bare schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose2/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Images for an event' restates the title 'Event Images' without adding a verb or clear action. It fails to specify whether the tool retrieves, lists, or uploads images, making it essentially tautological.
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 is provided about when to use this tool versus alternatives like 'event' or 'event_search'. The description gives no context on prerequisites, selection criteria, or exclusions, leaving the agent without direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
C2.9/5.0
Disambiguation2/5
The tools fall into two unrelated domains (Ticketmaster event discovery and Pipeworx data research), and within the Pipeworx set there are near-duplicate tools like ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded, plus multiple overlapping prediction-market tools (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, etc.). An agent would struggle to choose among these overlapping options and may not realize that most tools are unrelated to the server's stated name.
Naming Consistency3/5
Naming uses consistent snake_case, but the pattern is mixed: Ticketmaster resource fetchers are bare nouns (event, venue, attraction, classification) while search tools use verb_noun (event_search, venue_search). Pipeworx tools vary between verb phrases (ask_pipeworx, validate_claim) and descriptive noun phrases (entity_profile, polymarket_kalshi_spread). This inconsistency makes predicting tool names harder, though each name is still readable.
Tool Count2/5
41 tools is excessive for a server titled 'Ticketmaster' when only about 10 are Ticketmaster-related; the other 30 cover an entirely different service (Pipeworx). The count is far beyond a focused scope and suggests the server should be split into two separate, well-scoped MCP servers.
Completeness4/5
For the Ticketmaster half, the surface is complete for read-only event discovery (search events/venues/attractions, get single resources, classifications, autocomplete). For the Pipeworx half, the tool suite is extensive, covering lookup, research, prediction markets, memory, subscriptions, and feedback. The only notable gap is the lack of any write operations, but this is consistent with the read-only nature of the underlying APIs.