Skip to main content
Glama

Events and holidays moving prices now

get_event_movers
Read-onlyIdempotent

The events and holidays lifting car hire rates most right now, across all 38 airports or one region or airport. For each: what it is, when, where, the car type that leads that airport, and how much dearer its pick-up dates are than comparable days in this morning's sweep, with where that stood at the first reading. Start here for 'what is moving car hire prices this week'.

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_event_movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoOptional. Only events, or only public and school holidays.
limitNoHow many to return. Default 15.
regionNoOptional. One of: Europe, North America, Latin America, Asia-Pacific.
airportNoOptional IATA code to keep to one airport.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, closed-world behavior, so the safety profile is covered. The description adds value the annotations cannot: the 38-airport coverage scope, the per-record payload contents, and data freshness framing ('this morning's sweep', 'where that stood at the first reading'). It does not discuss rate limits, auth, or result ordering, which keeps it below 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?

Three sentences, front-loaded with what the tool returns and what each record contains, then closing with the trigger question. Nearly every clause carries information, though 'with where that stood at the first reading' is awkwardly worded and the enumeration is dense enough to require a second read.

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?

With four optional parameters, no output schema, and a read-only annotation set, the description should describe scope and returned fields, which it does in detail. The remaining gap is the interaction between the region and airport filters and any ordering or freshness contract, but overall an agent has enough to call it correctly.

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 description coverage is 100% with all four parameters documented, so the schema carries the parameter burden and baseline 3 applies. The description adds only a weak implication that region and airport are scoping alternatives and that results can be events or holidays; it never states whether region and airport are mutually exclusive or which wins when both are passed.

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 names a specific resource and behavior: events and holidays currently lifting car hire rates, with scope 'all 38 airports or one region or airport'. It also enumerates what each result carries (identity, timing, location, leading car type, price delta versus comparable days, first-reading comparison). It stops short of explicitly distinguishing itself from siblings such as get_events, get_news_events, or get_promotion_days, relying only on 'Start here' as a precedence hint.

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?

'Start here for what is moving car hire prices this week' gives one concrete entry-point use case, which is real guidance rather than none. However, no sibling alternative is named, no when-not condition is offered, and the implied relationship to get_events / get_news_events is left for the agent to infer.

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