What's On Asia Events

Search events in a city by date range, category and keyword

search_events

Search verified events in one city. Results are sorted by start date and include the event page, the calendar (.ics) link, the verification date and, where the event page carries one, a booking link. Dates marked expected are expected dates, not yet confirmed by the organiser. If from_date and to_date are omitted, the window defaults to today through today plus 30 days in the city's local time. An empty result includes the nearest later date that does have events. This server is read-only: it takes no bookings, and prices and availability are confirmed on the merchant's site.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "city": "<city>"
    },
    "name": "search_events"
  }
}

Input Schema

Name	Required	Description
`city`	Yes	City slug or name from list_cities, for example "hong-kong".
`limit`	No	Maximum events to return. Default 10, maximum 25.
`keyword`	No	Optional keyword matched against the event name, local name, venue and short description.
`to_date`	No	End of the window, ISO date YYYY-MM-DD. Defaults to today plus 30 days in the city's timezone.
`category`	No	Optional category; one of the city's own category values, listed by list_cities.
`from_date`	No	Start of the window, ISO date YYYY-MM-DD. Defaults to today in the city's timezone.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.1/5.0

Behavior5/5

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

No annotations exist, so the description carries the full disclosure burden and does so well: sort order (start date), what each result contains, the meaning of 'expected' dates, default and empty-result behavior, and an explicit read-only/no-bookings statement with pricing deferred to the merchant. This is exactly the behavioral context the agent needs before calling.

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

Conciseness4/5

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

Front-loaded with purpose and scope in the first sentence, then progressively deeper detail on results and edge cases. Five sentences with minimal waste; the results-field enumeration is somewhat list-like but is justified given there is no output schema.

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

Completeness5/5

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

For a read-only search tool with no output schema, the description covers purpose, sorting, return shape, default window, empty-result fallback and the no-booking caveat. Nothing an agent needs in order to call this correctly is missing.

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%, including defaults, maximums and the category-to-list_cities relationship, so the schema already documents all six parameters. The description restates the default window and category provenance rather than adding syntax or format detail beyond the schema. Baseline 3 applies.

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

Purpose4/5

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

Opens with a specific verb and resource plus a scope qualifier: 'Search verified events in one city.' The 'verified' qualifier and single-city restriction make its remit concrete, and the title adds the date-range/category/keyword dimensions. It stops short of naming how it differs from siblings such as whats_on or event_details.

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

Usage Guidelines4/5

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

Gives real operational guidance: city values come from list_cities, omitted dates default to a 30-day window in the city's timezone, and an empty result returns the nearest later date. It does not explicitly say when to prefer this over whats_on or event_details, so the routing is implicit rather than stated.

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

All What's On Asia Events tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?