EventApp — events in Latvia

There are two near-duplicate pairs: 'search' vs 'search_events' (both keyword search over upcoming events) and 'fetch' vs 'get_event' (both return the full record of one event by id). The descriptions do acknowledge this and steer agents toward search_events and get_event, and events_happening_now is a reasonably distinct convenience view, so the boundaries are recoverable rather than genuinely ambiguous.

The set mixes bare-verb names (fetch, search) with verb_noun names (get_event, list_categories, list_cities, search_events) and one descriptive phrase (events_happening_now). It is readable but there is no single predictable pattern, which is why the aliased pairs look arbitrary rather than layered.

Seven tools is a sensible size for an events directory with browse, search and detail needs. However, roughly two of the seven (search and fetch) largely duplicate existing tools, so not every tool clearly earns its place.

The read-only lifecycle is well covered: discovery by category/city, keyword and date-filtered search, a 'happening now' view, and per-event details with venues, dates and ticket links. Gaps are minor edge conveniences (e.g. browsing by venue or organizer, or pagination for large result sets) that agents can work around via search_events.