Skip to main content
Glama

x420_weather_forecast

Retrieve official 7-day U.S. National Weather Service forecasts for a coordinate, including temperature, precipitation chance, wind, and detailed text.

Instructions

NWS forecast: Official 7-day forecast periods for a US coordinate from the National Weather Service API (free, no key): temperature, precipitation chance, wind, short and detailed text. Source: NOAA/NWS api.weather.gov. Not professional, legal, insurance, engineering, medical, financial or tax advice. PAID: $0.03 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: place, office, grid, periods[{name, start, end, temperature, precip_chance_pct, wind, short, detailed}] - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"lat":"32.7357","lon":"-97.1081","periods":"2"}.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "x420_weather_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYeslatitude
lonYeslongitude
periodsNo1–14 half-day periods (default 14)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

A4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the critical behavior: it is a paid call at $0.03 USDC settled on Base via x402, charges real money from X420_MCP_WALLET_PRIVATE_KEY, and returns the deliverable plus a signed receipt and settlement transaction. It also names the upstream provider and states the data is free/no-key at origin, which explains why the charge exists.

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 purpose, then source, then cost, then return shape, then example — a sensible order. It is dense and includes a long boilerplate disclaimer ('Not professional, legal, insurance...') plus a full return-field listing that pushes length, but almost every clause carries usable information.

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?

For a paid, no-output-schema tool, the description covers everything an agent needs: cost and payment mechanism, required env var, geographic scope, and a complete return shape (place, office, grid, periods fields). Return values are enumerated explicitly since no output schema exists.

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 coverage is 100%, so lat/lon/periods are fully documented in the schema, including the 1–14 half-day default. The description only repeats this via an example input and the 'periods' default, adding no new syntax or format semantics (e.g., string vs. numeric lat/lon expectations).

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?

States a specific verb and resource ('NWS forecast: Official 7-day forecast periods for a US coordinate'), names the upstream source (api.weather.gov), and scopes it geographically to the US. It does not explicitly route an agent away from the sibling x420_weather_alerts (alerts vs. forecast), leaving that distinction to be inferred from the tool names.

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?

Implied usage is clear (get a forecast for a US lat/lon), and the 'US coordinate' constraint plus 'free, no key' upstream hints at when this source is appropriate. However, there is no explicit statement of when to prefer this over x420_weather_alerts or other geo tools, and no guidance on cost-based alternatives.

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