Skip to main content
Glama

X420 agent services

x420_weather_forecast

Read-onlyIdempotent

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. Price: $0.03 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: place, office, grid, periods[{name, start, end, temperature, precip_chance_pct, wind, short, detailed}].

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 observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world and non-destructive behavior, but the description adds the facts an agent most needs and cannot get from annotations: the tool is a paywalled stub that returns payment instructions rather than weather data, the price is $0.03 USDC per call via x402 on Base, and an alternative local-server path exists. This is exactly the kind of behavior-beyond-annotations disclosure the dimension rewards. The legal disclaimer sentence is boilerplate but harmless.

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?

Purpose is front-loaded before payment mechanics and deliverable shape, which is the right ordering, and almost every sentence carries operational information. The legal disclaimer clause and the density of parenthetical payment details add some noise, but nothing is genuinely wasted.

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?

There is no output schema, yet the description spells out the exact deliverable shape (place, office, grid, periods with named fields), so the agent knows what it gets once paid. Combined with the pricing and payment-flow explanation, nothing needed to invoke this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so lat/lon/periods are already documented and the baseline is 3. The description adds a real constraint beyond the schema: the coordinate must be a US coordinate, which bounds valid input in a way the schema does not. It adds nothing further about formats, so it does not reach a 5.

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 first sentence names a specific verb and resource: official 7-day forecast periods for a US coordinate from the NWS API, and enumerates the returned weather fields. That is far more specific than a restated name. It never mentions the sibling x420_weather_alerts, so an agent must infer the forecast/alerts split from the names alone.

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?

It gives explicit operational guidance for how to actually obtain the deliverable: GET the url, read PAYMENT-REQUIRED from the 402, retry with PAYMENT-SIGNATURE, or run the local x420-mcp server with a wallet key. It also states this hosted tool does not pay and does not return the data, which prevents a common misuse. It gives no when-to-use/when-not guidance relative to sibling weather tools, so the bar for a 5 is not met.

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