Skip to main content
Glama
Sign In

What's On Asia Events

by com.whatsonasia
OverviewDiscussionsAdmin

List cities covered by What's On Asia Events

list_cities

List the cities this server covers, with the site that publishes each city's events, the regions covered, how many upcoming events are listed, the earliest and latest upcoming dates, the published languages, and how fresh the data is. Call this first to discover valid city values for the other tools. This server is read-only: it takes no bookings and confirms no prices.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_cities"
  }
}

Input Schema

NameRequiredDescriptionDefault
languageNoOptional language hint. Accepted for convenience; it does not filter the results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/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 largely meets it: it declares the server is read-only and takes no bookings and confirms no prices, and it notes that the language argument "does not filter the results." Minor gaps remain around result volume limits, but the safety and non-transactional profile is clearly disclosed.

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 the verb and resource, then a single dense enumeration of return fields, followed by two short, purposeful sentences on usage and read-only status. The field list is long but every item is informative, so nothing is wasted.

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?

Complete for a one-parameter, zero-required discovery tool with no output schema: it describes what is returned, when to call it, and the read-only, no-booking, no-price behavior. Nothing an agent needs in order to invoke it 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% and the single optional language parameter is already documented there as a non-filtering hint. The description reinforces the multilingual aspect only indirectly by listing "published languages" among the returned fields, so it adds little meaning beyond the schema. Baseline 3 applies.

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

Purpose5/5

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

Opens with a specific verb and resource ("List the cities this server covers") and then enumerates exactly what each entry carries: publisher site, regions, event counts, date range, languages, and freshness. An agent can tell this is a discovery/enumeration tool without opening the schema.

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

Usage Guidelines5/5

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

Explicitly states the sequencing rule: "Call this first to discover valid city values for the other tools." That gives a concrete condition for when to use it and why it precedes siblings like search_events. No exclusions are needed for a discovery tool of this kind.

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