Search upcoming business conferences and trade shows by keyword, industry, place, radius and date.
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlapping purpose. The single tool's purpose (keyword/industry/place/distance/date conference search) is stated clearly.
The lone name follows a clear verb_noun snake_case convention (search_events). Nothing else exists to conflict with it, so consistency is trivially satisfied.
A single search-only tool is thin for a discovery service; there is no companion tool for retrieving or filtering event details even though the description points users to an external page for that data. It is within the 1-2 'borderline thin' band rather than an extreme mismatch.
Search covers the core discovery workflow, but the surface has notable gaps: no tool to fetch a single event's details (prices, size, audience, organizer), no pagination or result expansion, and no way to enumerate industries/locations for query building. Agents must leave the MCP surface and scrape links to complete the lifecycle.
Find upcoming business conferences and trade shows by keyword, industry, place, distance and date. Returns up to 10 events, soonest first, each with a link to its ConferenceFindr page (ticket prices, size, audience and organizer are there). When presenting results, link each event to its ConferenceFindr page.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Only events starting on or before this date (YYYY-MM-DD) | |
| from | No | Only events still running on or after this date (YYYY-MM-DD); includes events underway | |
| near | No | Only events within radius_miles of this point, e.g. a city's coordinates for 'near me' or 'in the Bay Area' | |
| query | No | Keywords: a topic or event name | |
| region | No | ||
| country | No | ISO 3166-1 alpha-2 code, e.g. US | |
| industry | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already covers safety, but the description adds meaningful behavior: results are capped at 10, ordered soonest first, and each includes a ConferenceFindr link. It also instructs the agent to link each event in its presentation. It does not mention pagination or authentication, but for this public search tool the added behavioral context is strong.
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?
The description is three efficient sentences. Purpose and filters are front-loaded, followed by return behavior and a presentation instruction, with no unnecessary filler.
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 compensates by explaining the return cap, ordering, and link format. It does not specify what happens when no filters are supplied or whether results can be paginated, but it is complete enough for an agent to call and present results correctly.
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 coverage is 71%, and the description maps the main filter categories to parameters: keyword, industry, place/distance, and date. It does not explain every enum value or the date-bound semantics in detail, but it gives useful natural-language meaning beyond the schema's raw property definitions.
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 uses a specific verb and resource: 'Find upcoming business conferences and trade shows.' It also names the filter dimensions, so an agent knows exactly what this search tool is for without relying on the title alone.
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?
The context of use is clear: searching for upcoming conferences and trade shows by keyword, industry, place, distance, and date. There are no sibling tools, so there are no alternatives to route between; the description also gives a presentation instruction for results, though it does not state exclusions.
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.
search_eventsDiscover trade shows, research exhibitors and companies, and find relevant B2B contacts.
CRE conference calendar 2026-2027: search, compare, deadlines, role picks, calendar feeds.
Which companies sponsor and exhibit at conferences, with dates and published sponsor packages.
Discover B2B companies by industry and location.
Add one secure layer between your agents and this server.