EventMatey Event Discovery

search_events_nearby

Search EventMatey events by location. The current v1 implementation uses location_text plus date/category/price filters. Latitude/longitude and radius are accepted for forward compatibility but are not yet used for true distance search.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum number of events to return
`end_date`	No	Optional inclusive end date in YYYY-MM-DD format
`latitude`	No	Optional latitude for future geo-capable search
`longitude`	No	Optional longitude for future geo-capable search
`radius_km`	No	Optional search radius in kilometres for future geo-capable search
`categories`	No	Optional category or tag filters
`start_date`	No	Optional inclusive start date in YYYY-MM-DD format
`location_text`	No	Use this for the current v1 location search, such as Bristol or Leeds
`max_price_gbp`	No	Optional maximum price in GBP
`min_price_gbp`	No	Optional minimum price in GBP

TDQS

A4.2/5.0

Behavior4/5

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

Discloses that lat/lon/radius are accepted but not used in v1, making the tool's current limitations transparent. Without annotations, this is valuable behavioral context.

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 sentences with no redundancy: first states core function, second explains limitations and future plans. Efficient and well-structured.

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 essential behavior and limitations. Lacks mention of result format or pagination, but this is partly covered by the 'limit' parameter in schema. Sufficient for a simple search tool with good schema coverage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds meaningful context beyond schema descriptions, e.g., clarifying that location_text is the primary parameter for v1 and that geospatial parameters are forward-compatible placeholders.

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 events by location, distinguishing itself from siblings like search_events_by_keyword which likely uses different criteria.

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?

Does not explicitly compare with sibling tools or state when to use this vs alternatives. The 'v1 implementation' hint guides usage but lacks direct when/when-not 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 tools Inspect

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

Need Help?