Skip to main content
Glama

Events and holidays, with what they are doing to rates

get_events
Read-onlyIdempotent

Events (trade fairs, concerts, sport, festivals, with venue, expected crowd and whether the crowd flies in), public and school holidays, and news events (a ground stop, a strike, a storm, with what each did to rates) for an airport over a date range. For those inside the 14 pick-up days of this morning's sweep it also gives the lift now: how much dearer their pick-up dates are than comparable days. Also says how much of the airport's overseas visitor base is on holiday at home in that window and whether locals are off. Default: today to 90 days ahead.

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": {
      "airport": "<airport>"
    },
    "name": "get_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNo
fromNo
airportYesIATA airport code, e.g. AKL, SYD, LHR, MAD. See list_airports.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. Beyond that the description discloses genuinely non-obvious behavior: the default window of today to 90 days ahead, and that lift figures are only returned for items inside the 14 pick-up days of this morning's sweep, plus the overseas-visitor-on-holiday and locals-off indicators. It does not mention response size, pagination, or how 'comparable days' are chosen, 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?

Front-loaded with the resource and scope, and every clause carries content — the parentheticals specify crowd type and rate effect rather than padding. It is a long run-on of stacked clauses rather than cleanly segmented sentences, so it reads dense, but little could be cut without losing real information.

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?

There is no output schema, and the description compensates by narrating what comes back: event type, venue, crowd size and origin, holiday types, rate effect of news events, and derived lift and holiday-base metrics. Combined with a partial default for the date range, an agent has what it needs to call it correctly; only the date format and result size remain unstated.

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 only 33% — only airport is documented in the schema (IATA code, pointing at list_airports). The description partially compensates by defining the from/to window via the default 'today to 90 days ahead', but it never states the accepted date format or the maximum span allowed, so an agent still has to guess at the two undocumented parameters.

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?

States a specific resource set (events, holidays, news events) plus scope (an airport over a date range) and enumerates the data carried (venue, expected crowd, whether the crowd flies in, what each did to rates). An agent can tell this is the events/holidays-plus-rate-impact feed. It stops short of distinguishing itself from the sibling get_news_events, which the phrase 'news events' overlaps with, leaving that boundary for the agent to infer.

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 is implied rather than stated: the description makes clear you call this to explain rate movements around an airport's events and holidays, and it supplies a default range ('today to 90 days ahead'), which is a real invocation aid. But it never says when to prefer this over get_news_events, get_event_movers, or get_market_snapshot, and gives no exclusions or prerequisites.

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