Skip to main content
Glama

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
Behavior4/5

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

Beyond the readOnly/openWorld annotations, the description discloses the upstream source (NOAA NWS, official US government data), the forecast horizon (7 days), the geographic limit (US only), the per-call price ($0.10 USDC), and the shape of the answer. It does not state latency, caching, or what happens when geocoding of a concatenated address fails, which is the main residual uncertainty.

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 trigger condition, followed by method, output, and a concrete worked example — every block has a purpose. The example and the reschedule advice run a bit long, but they carry real decision value rather than filler.

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 compensates by describing the return (risk tier and specific high-risk days) and grounding it in a sample response. The remaining gap is that all three parameters are optional yet at least one of location or the lat/lon pair is clearly required for a meaningful call, and the description never says so.

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 lat/lon/location are already fully documented and the baseline is 3. The description adds only the implicit US-only constraint on location; it never mentions that lat and lon are a bypass pair or what to do when neither is supplied.

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 a specific verb and resource — analyzing NOAA 7-day forecast data against construction delay thresholds — and names the exact return artifacts (risk tier plus high-risk days). The thresholds (precipitation probability, wind >25 mph, freeze <32°F) make it unmistakable against generic climate-risk siblings.

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?

Explicit when-to-use triggers are given: scheduling outdoor construction, planning equipment deployment, assessing weather risk for a US site. What is missing is any exclusion or pointer to an alternative tool (e.g., long-range climate scoring vs. 7-day operational forecast), so the agent must infer the boundary itself.

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