Skip to main content
Glama

EventMatey Event Discovery

by com.eventmatey.mcp

search_events_by_keyword

Search public EventMatey events by keyword, optional UK location text, date range, categories, and price range. Returns only published and bookable events that the organiser has enabled for AI discovery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of events to return
keywordYesKeyword or phrase to search for, such as baking class or live music
end_dateNoOptional inclusive end date in YYYY-MM-DD format
categoriesNoOptional category or tag filters
start_dateNoOptional inclusive start date in YYYY-MM-DD format
location_textNoOptional UK location hint such as Bristol, Manchester, or London
max_price_gbpNoOptional maximum price in GBP
min_price_gbpNoOptional minimum price in GBP

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses that only published, bookable events enabled for AI discovery are returned, which adds value beyond schema. No annotations provided, so description carries the burden. Does not cover rate limits or result ordering.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences with front-loaded purpose. No redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers core functionality and return filter. Lacks pagination or ordering details, but limit parameter is in schema. Adequate for a search tool.

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?

Schema coverage is 100%, so parameters are fully documented. Description reiterates parameter types without adding new meaning beyond schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states the tool searches public EventMatey events by keyword with optional filters. Distinguishes from sibling tools 'search_events_nearby' (location-based) and 'get_event_details' (specific event info).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implies usage for keyword-based searching but does not explicitly contrast with siblings or provide when-to-use/when-not-to-use guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All EventMatey Event Discovery toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a distinct purpose: get_event_details retrieves details for a specific event, search_events_by_keyword enables keyword-based search, and search_events_nearby is location-focused. No overlap in primary functionality.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern: get_event_details, search_events_by_keyword, search_events_nearby. The verbs (get, search) are appropriate for the actions and are uniformly used.

Tool Count5/5

Three tools is an appropriate and well-scoped set for an event discovery service, covering detail retrieval and two distinct search methods without unnecessary redundancy.

Completeness4/5

Core discovery operations are covered: keyword search, location search, and event details. Minor gap is absence of a tool to list available filter options (e.g., categories), but overall surface is sufficient for typical use cases.

Resources