Skip to main content
Glama

Stratalize Intelligence

Get Weather Delay Risk

get_weather_delay_risk
Read-only

Use when scheduling outdoor construction work, planning equipment deployment, or assessing weather risk for any US project site. Analyzes NOAA 7-day forecast data against construction delay thresholds — precipitation probability, wind speed above 25 mph, and freeze events below 32°F — returning a risk tier and specific high-risk days to avoid. Example: Chicago IL project site shows HIGH delay risk Thursday through Saturday — 70% precipitation probability, 2.3 inches rain forecast, 28°F overnight low Friday. Reschedule concrete pours and crane operations. Source: NOAA National Weather Service — official US government forecast. $0.10 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
latNoOptional WGS84 latitude; use with lon to bypass geocoding
lonNoOptional WGS84 longitude; use with lat to bypass geocoding
locationNoUS city and state, or full street address (e.g. Miami, FL or 1600 Pennsylvania Ave Washington DC)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds substantial context beyond them: the authoritative data source (NOAA/NWS), the exact thresholds used (precipitation probability, wind above 25 mph, freeze below 32°F), the geography restriction to US sites, and per-call pricing of $0.10 USDC. The cost disclosure in particular is behaviorally important and unavailable from any structured field.

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?

It is front-loaded with the usage trigger and purpose before the example, source, and price. The worked Chicago example is longer than strictly necessary but demonstrates the return shape, which has value given there is no output schema; overall it earns most of its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 must convey return values and does so clearly (risk tier plus specific high-risk days, illustrated with concrete numbers). Combined with the source, US-only scope, and cost, an agent has enough to decide to call it and to interpret the result.

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 lat/lon and location already documented including the geocoding bypass, so the schema carries the parameter burden. The description adds only the implicit constraint that the site must be in the US, without clarifying precedence between lat/lon and location or what happens when both are omitted (zero required 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?

The description states a specific verb and resource: it analyzes NOAA 7-day forecast data against construction delay thresholds and returns a risk tier plus high-risk days. The construction-scheduling framing separates it in practice from generic risk siblings like get_climate_risk_score or get_climate_risk_benchmark, but those adjacent tools are never named or contrasted, so the differentiation is implicit rather than explicit.

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?

The opening sentence gives explicit use cases (scheduling outdoor construction work, planning equipment deployment, assessing weather risk for a US project site) and the example adds a concrete action ('Reschedule concrete pours and crane operations'). There are no when-not-to-use conditions or named alternative tools, which keeps it short of a 5.

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