MCP Live Events Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TICKETMASTER_API_KEY | Yes | Your Ticketmaster API key (also called 'Consumer Key' on the Ticketmaster developer portal) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_upcoming_eventsB | Get upcoming music events for a city. Args: city: City in which to search for events. start_dttm_str: Start date/time in ISO 8601 format (YYYY-MM-DDTHH:MM:SSZ). Example: 2025-02-08T00:00:00Z end_dttm_str: Start date/time in ISO 8601 format (YYYY-MM-DDTHH:MM:SSZ). Example: 2025-02-10T00:00:00Z keyword: Any optional keywords to help filter search results. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool's purpose is clearly defined as retrieving upcoming music events for a specified city, making it distinct by default.
The single tool name 'get_upcoming_events' follows a clear verb_noun pattern (get + upcoming_events), which is consistent within this minimal set. There are no other tools to compare against, so no inconsistency exists.
A single tool is too few for a server named 'MCP Live Events Server', which suggests a broader domain of live events management. This minimal toolset feels thin and incomplete for handling events beyond basic retrieval, such as creating, updating, or deleting events.
The tool surface is severely incomplete for the implied domain of live events. While 'get_upcoming_events' allows retrieval, there are significant gaps: no tools for creating events, updating event details, deleting events, or managing other aspects like tickets or venues, which will likely cause agent failures in comprehensive workflows.