etix-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| etix_searchA | Search Etix by keyword and get matching events (performances), venues, and performers — each with its id and canonical etix.com URL. Follow up with etix_get_event (event_id) or etix_get_venue (venue_id) for full details. Backs onto Etix's public suggest endpoint; returns a few top matches per category, not an exhaustive list. Read-only, no Etix account required. |
| etix_get_eventA | Fetch a single Etix event (performance) by its numeric event_id — name, date/time, venue (with address + coordinates), organizer, ticket price range and the individual priced offer levels. Get the event_id from etix_search. Read-only, no Etix account required. |
| etix_get_venueA | Fetch a single Etix venue by its numeric venue_id — name, organizer, full address, and the list of upcoming events at that venue (each with event_id, name, start time, and ticket URL). Get the venue_id from etix_search. Follow up with etix_get_event for any listed event. Read-only, no Etix account required. |
| etix_find_locationA | Resolve a city name or postal code to coordinates (latitude/longitude) plus the normalized city/state, using Etix's geolocation lookup. Useful as a building block for location-based event browsing. Returns found:false with a message when nothing matches. Read-only, no Etix account required. |
| etix_healthcheckA | Round-trips a small public www.etix.com URL (/robots.txt) through ContextMint Bridge (your signed-in browser tab) and returns diagnostics: the bridge's role (host/peer/null), port, version, the extension link (linked / pair pending / not attached / never answered), the elapsed round-trip time, and a plain-English hint distinguishing 'bridge never came up' from 'extension not connected' from 'this browser can't serve a capability' from 'real www.etix.com-side problem'. Read-only, no auth required. Call this when a real tool fails and you want to know which hop broke. |
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 5 tools
The four Etix domain tools are largely distinct: search is a discovery entry point, get_event and get_venue are ID-based detail lookups, and healthcheck is an explicit diagnostic utility. The main wrinkle is etix_find_location, which returns coordinates but has no consuming tool, leaving its role somewhat orphaned.
All tools share the etix_ prefix and are mostly verb_noun (find_location, get_event, get_venue), which is predictable. Minor deviations are etix_search (bare verb) and etix_healthcheck (noun, no verb_noun form).
Five read-only lookup/diagnostic tools is a compact, well-scoped set with no obvious redundancy. It is a touch thin for an event-browsing surface, but each tool earns its place.
The read-only discovery surface covers search, event detail, venue detail, and connectivity diagnostics, but find_location produces coordinates that no other tool accepts, and there is no way to browse events by city, date, or category. These are notable gaps for location-based event browsing, which the description explicitly advertises.