mcp-livedatapro

getHyperlocalWeather

Aviation METAR/TAF and hyperlocal 48-hour weather, wind gusts, visibility, and precipitation risk. Use when requesting current meteorological telemetry, aviation METAR/TAF strings, wind gusts, and 48-hour hyperlocal precipitation forecasts. Do not use for historical climate archives or airport gate delays (use getLiveFlights). Updates every 10 minutes from WMO/aviation stations and returns metric units (°C, km/h, meters).

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": {
      "location": "<location>"
    },
    "name": "getHyperlocalWeather"
  }
}

Input Schema

Name	Required	Description	Default
`location`	Yes	City name, GPS coordinates (lat,lon), or 4-letter Airport ICAO / 3-letter IATA code.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 24, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```
- addedInput schema / properties / location / examples
```
Added value: +[
+  "LHBP"
+]
```
- addedInput schema / properties / location / minLength
```
Added value: +2
```

Changed1 schema field changedOct 24, 2026

changedInput schema / properties / location / description

Previous value: -"City name, coordinates (lat,lon), or Airport ICAO/IATA code"New value: +"City name, GPS coordinates (lat,lon), or 4-letter Airport ICAO / 3-letter IATA code."

First observedOct 21, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries the full burden, and it delivers: refresh cadence every 10 minutes, data provenance from WMO/aviation stations, and metric output units (°C, km/h, meters). It does not mention authentication, rate limits, or how invalid location codes are handled, so a small gap remains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three sentences, front-loaded with what the tool returns before moving to usage and exclusions. Every sentence contributes distinct information: capability, selection criteria, and operational characteristics.

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?

No output schema or annotations exist, so the description must describe return content, and it names METAR/TAF strings, gusts, visibility, precipitation, and units. The exact response structure and field layout remain unspecified, but enough is given to invoke and interpret the call.

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?

The single location parameter has 100% schema description coverage including an ICAO example, so the schema does the heavy lifting and the baseline is 3. The description's mention of aviation stations and METAR/TAF implies ICAO codes, but that meaning is already in the schema and no new syntax or format guidance is added.

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 specific verbs and resources: retrieves aviation METAR/TAF strings plus 48-hour hyperlocal weather, wind gusts, visibility, and precipitation risk. It explicitly contrasts with getLiveFlights and historical archives, so an agent can separate it from sibling tools 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?

Contains an explicit 'Use when requesting...' clause and a 'Do not use for historical climate archives or airport gate delays (use getLiveFlights)' exclusion naming the alternative. Both the positive trigger and the boundary condition are stated outright.

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

All mcp-livedatapro tools Inspect

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

Need Help?