Skip to main content
Glama

News events and what they did to prices

get_news_events
Read-onlyIdempotent

Travel disruptions read from the news in the last two weeks (a nationwide ground stop, an air traffic control strike, an airport closure, a storm), and what each did to car hire rates and availability at the airports it touched. Use it for questions like 'what did the FAA ground stop do to rental car prices'. It compares the same pick-up dates in the last sweep before the news with the sweeps after it. An answer of no measurable move is a real finding: say so plainly.

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

Input Schema

NameRequiredDescriptionDefault
airportNoOptional IATA code to keep to one airport.
countryNoOptional two-letter country code, e.g. US, GB, FR, AU.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond that: it discloses the comparison methodology (same pick-up dates, last sweep before the news versus sweeps after) and, importantly, that 'no measurable move' is a legitimate result the agent should report rather than treat as failure. It does not mention limits on how many events come back or how sparse coverage may be.

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 first sentence front-loads the resource and its scope, followed by a usage example and then the methodology and the null-result caveat in a logical order. The parenthetical list of disruption types is slightly illustrative padding but does usefully bound what counts as an event. No sentence is redundant with the annotations.

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 no output schema, the description correctly spends its words on what the answer represents: a before/after comparison on matched pick-up dates, with a null finding treated as a valid answer. For a two-optional-parameter read-only tool this is close to sufficient. The only gap is the absence of any indication of result volume or event coverage breadth.

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%, so both optional parameters (airport IATA code, two-letter country code) are already documented in structured form. The description only alludes to airports indirectly ('at the airports it touched') and adds no scoping semantics beyond what the schema states. Baseline 3 applies when the schema carries the parameter burden.

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 (travel-disruption news events from the last two weeks) and a specific outcome it reports (what each event did to car hire rates and availability at affected airports). An agent can tell this is a news-to-price-impact tool rather than a raw event list or a rate lookup. It stops short of naming a sibling such as get_events or get_event_movers to draw the boundary explicitly.

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?

Usage is anchored by a concrete example question ('what did the FAA ground stop do to rental car prices') plus the two-week recency window, which tells the agent the right context to invoke it in. There are no exclusions or named alternatives for cases like 'I want the raw event list' or 'I want current rates', so the agent must infer the boundary from sibling names alone.

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