Skip to main content
Glama
Sign In

What's On Asia Events

by com.whatsonasia
OverviewDiscussionsAdmin

What is on in a city: today, this weekend, this week or the next 7 days

whats_on

Answer the common question "what is on in this city" over a named window, using fixed definitions in the city's local time: this_weekend means Friday to Sunday; if today is Saturday or Sunday it means the current weekend, otherwise the coming one. this_week means today through the coming Sunday. next_7_days means today through today plus 6 days. today means today only. Results are sorted by start date and include the event page, 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. 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": "whats_on"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity slug or name from list_cities, for example "hong-kong".
whenNoNamed window. Default this_weekend.
limitNoMaximum events to return. Default 10, maximum 25.
categoryNoOptional category; one of the city's own category values, listed by list_cities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so well: it declares the server read-only, states no bookings are taken, explains that prices and availability are confirmed on the merchant's site, discloses sort order (by start date), lists returned fields (event page, verification date, optional booking link), and explains that 'expected' dates are unconfirmed by the organiser.

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?

The core purpose is front-loaded, followed by window definitions and then the read-only caveats in a logical order. The window definitions are dense but each clause carries distinct information; there is little filler, though the sentence chain could be tightened.

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?

For a four-parameter read-only lookup with no output schema, the description covers purpose, window semantics, return contents, sorting and the key caveat about unconfirmed dates, which is enough to call it correctly. Minor gaps remain around behaviour when no events match or how category values are validated, but nothing critical is missing.

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?

Schema coverage is 100%, so the schema baseline already documents city, when, limit and category. The description goes beyond it by giving the exact calendar semantics of each `when` value (Friday–Sunday, weekend rollover rules, today+6 days) and by anchoring them to the city's local time, which the schema does not state.

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?

The description states a specific verb and resource: answering 'what is on in this city' for a named time window, with each window defined precisely in local time. It is clearly distinguishable in substance from a free-form event search, but it never names search_events or event_details, so differentiation is left to inference.

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?

Usage context is implied by 'Answer the common question "what is on in this city"' and by the enumeration of the four named windows, which tells the agent what inputs are appropriate. However, there is no explicit guidance on when to choose this tool over search_events or event_details, and no stated exclusions.

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 toolsInspect
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