Local US events by town, date and kind (trivia, live music, karaoke...), each checked at its source.
Scored across 1 tool
With a single tool there is nothing to confuse it with, and its purpose (find events near a US town on a given date) is stated unambiguously. An agent can immediately tell when this tool applies and when it does not.
The lone name follows a clear verb_noun convention (find_events) in snake_case, which is immediately readable. There is no competing convention to clash with it.
One tool is thin for an event-discovery domain; the single search tool carries all the weight for town/date/kind filtering plus citation metadata. It is not trivial, but the surface feels under-scoped for anything beyond a one-shot lookup.
Search is covered well (town, ZIP, date, event kind, source citation), but there is no way to fetch details for a specific result, list available event categories, or query a date range. Agents hitting a promising result have no follow-up operation and must work around the gap.
Things to do on one day near one US town (trivia, live music, karaoke, comedy, games, markets, talks and more), each checked against the page it came from. Give a town ("Columbus, OH" or a 5-digit ZIP), a date, and optionally a kind of event. Each result has its own Suumer page to cite (suumerPage), and the original source page when we can show it.
| Name | Required | Description | Default |
|---|---|---|---|
| date | No | The day, written YYYY-MM-DD. Leave it out for today in that town. | |
| kind | No | Kind of event. Leave it out (or "all") for everything. | |
| town | Yes | A US town and state, like "Columbus, OH", or a 5-digit ZIP code. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: each event is checked against the page it came from, and results carry a Suumer page plus the original source. It doesn't discuss coverage gaps or rate limits, keeping it short of a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with scope, then inputs, then return shape. The event-type parenthetical earns its place by showing breadth without listing the whole enum, and nothing is repeated.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description does the needed work by naming the return fields (suumerPage, original source page) and the verification step. Only minor gaps remain, such as result volume or how verification failures appear.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the three parameters (town format, YYYY-MM-DD date with today-default, kind enum with leave-out default) are fully documented in structured data. The description restates the town formats and defaults but adds no syntax or semantics beyond the schema, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb+resource (find things to do / events) with tight scope: one day, one US town. The parenthetical event-type list and the verification claim make the tool's job unambiguous, and there are no siblings to confuse it with.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It makes clear the required inputs (town plus date) and the optional kind, and documents defaults in prose ("Leave it out for today in that town", kind omission = everything). It does not state when NOT to use the tool, but there are no alternatives to route against.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
find_eventsHyper-local events and venues (trivia, open mics, readings, gigs) for US metros and London.
Free US local event search. No signup or API key; 90-day lookahead. Paid commercial and bulk access.
250,000+ real, local, future events, ranked for the signed-in person. Free to connect.
Live LA events, ticket price comparison, bars & nightlife with real-time happy hours
Add one secure layer between your agents and this server.
