Skip to main content
Glama

What's on in Hong Kong

get_events
Read-only

Big events in Hong Kong (concerts at the major venues, sports, festivals, arts), the same list as getaroundhongkong.com/events: titles in five languages, dates, venue, coordinates, nearest MTR station, and this site's page for getting there. Filter by dates (events overlapping from–to, Hong Kong dates, YYYY-MM-DD; from today on by default) and featured (the biggest, most crowded ones).

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": "get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day, YYYY-MM-DD (default: everything coming up)
fromNoFirst day, YYYY-MM-DD (default today)
featuredNoOnly the featured (biggest) events

Output Schema

NameRequiredDescriptionDefault
toYesLast day covered, or null for everything coming up
fromYesFirst day covered, YYYY-MM-DD (Hong Kong)
eventsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedOutput schema / properties / events / items / properties / time / description
      Previous value: -"Start time HH:MM, Hong Kong, where known"New value: +"Start time HH:MM, Hong Kong, where known (the first show's, where it differs by night)"
    • addedOutput schema / properties / events / items / properties / times
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {
      +        "type": "string"
      +      },
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Start time HH:MM by date (YYYY-MM-DD) where shows start at different times; null when every day is the same"
      +}
    • changedOutput schema / properties / events / items / required
      Previous value: -[
      -  "id",
      -  "kind",
      -  "title",
      -  "start",
      -  "end",
      -  "time",
      -  "ends",
      -  "venue",
      -  "lat",
      -  "lon",
      -  "station",
      -  "url",
      -  "link",
      -  "featured",
      -  "image"
      -]New value: +[
      +  "id",
      +  "kind",
      +  "title",
      +  "start",
      +  "end",
      +  "time",
      +  "times",
      +  "ends",
      +  "venue",
      +  "lat",
      +  "lon",
      +  "station",
      +  "url",
      +  "link",
      +  "featured",
      +  "image"
      +]
  2. Changed3 schema fields changed
    • addedOutput schema / properties / events / items / properties / ends
      Added value: +{
      +  "description": "Roughly when it ends each day, HH:MM, Hong Kong: from its running time, else about 2.5 hours after a concert starts; null if not known",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / events / items / properties / image
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": false,
      +      "properties": {
      +        "credit": {
      +          "description": "Whose picture it is: credit it when showing it",
      +          "type": "string"
      +        },
      +        "focus": {
      +          "description": "Where to centre a crop, CSS background-position",
      +          "type": "string"
      +        },
      +        "height": {
      +          "type": "number"
      +        },
      +        "source": {
      +          "description": "The page it's from: link to it when showing it",
      +          "type": "string"
      +        },
      +        "url": {
      +          "description": "The event's own picture (its organiser's artwork), on this site",
      +          "type": "string"
      +        },
      +        "width": {
      +          "type": "number"
      +        }
      +      },
      +      "required": [
      +        "url",
      +        "width",
      +        "height",
      +        "credit",
      +        "source"
      +      ],
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "description": "Featured events' pictures; null until one is found"
      +}
    • changedOutput schema / properties / events / items / required
      Previous value: -[
      -  "id",
      -  "kind",
      -  "title",
      -  "start",
      -  "end",
      -  "time",
      -  "venue",
      -  "lat",
      -  "lon",
      -  "station",
      -  "url",
      -  "link",
      -  "featured"
      -]New value: +[
      +  "id",
      +  "kind",
      +  "title",
      +  "start",
      +  "end",
      +  "time",
      +  "ends",
      +  "venue",
      +  "lat",
      +  "lon",
      +  "station",
      +  "url",
      +  "link",
      +  "featured",
      +  "image"
      +]
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the bar is lower; the description still adds real context beyond them – the data source, the default date window (from today forward), and the overlap semantics of the range. It omits result volume/pagination expectations, which keeps it from 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.

Conciseness4/5

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

Two sentences, front-loaded with the resource before the filter semantics, and every clause carries information. The long parenthetical list of field names and venue examples is dense and slightly harder to scan than necessary.

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?

An output schema exists, so return values needn't be explained, and the description covers scope, defaults, and filter behavior. What remains unstated is anything about result size or ordering, a minor gap for a list-style tool.

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 baseline is 3, but the description earns more: it clarifies that from/to match events *overlapping* the range (not just starting within it), that dates are Hong Kong dates in YYYY-MM-DD, and that 'featured' means biggest/most crowded rather than merely popular.

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?

States a specific resource (big events in Hong Kong: concerts, sports, festivals, arts) and explicitly names the data source ('the same list as getaroundhongkong.com/events'), plus the fields returned. None of the siblings (border_crossings, search_routes, plan_trip, etc.) overlap with this, so an agent can route to it 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 Guidelines4/5

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

Gives clear operating context: filter by date range with 'from today on by default', and use featured for 'the biggest, most crowded ones'. It never names an alternative tool or a when-not-to-use case, but the domain is narrow enough that no exclusion is really needed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources