Eventfinda MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVENTFINDA_PASSWORD | Yes | Your Eventfinda API password from https://www.eventfinda.co.nz/api/v2/index | |
| EVENTFINDA_USERNAME | Yes | Your Eventfinda API username from https://www.eventfinda.co.nz/api/v2/index |
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 |
|---|---|
| list_eventsB | List all events within this week for a given location. |
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, as there are no other tools to compare it to. The tool's purpose is clearly defined and distinct by default.
The single tool follows a consistent verb_noun pattern (list_events), and with no other tools, there is no inconsistency in naming conventions. The naming is straightforward and predictable.
A single tool is too few for a server named 'Eventfinda MCP', which implies a broader scope for event discovery and management. This minimal toolset likely leaves significant gaps in functionality, such as searching, filtering, or accessing event details beyond this week.
The tool surface is severely incomplete for an event-finding domain. It only lists events for this week in a given location, missing essential operations like searching events by date range, category, or keyword, getting event details, or managing user interactions.