Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

US weather forecast for a point in one call from the National Weather Service: current hour and the next 8 forecast peri

weather_forecast
Read-onlyIdempotent

US weather forecast for a point in one call from the National Weather Service: current hour and the next 8 forecast periods with temperature, wind, precipitation chance, short and detailed forecast, city, state and forecast office (lat=40.7128, lon=-74.0060). US points use the National Weather Service, other points MET Norway (CC BY 4.0). Forecast, not a warning service. Pay per call $0.002 USDC on Base via x402.

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": "weather_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
latNolatitude, e.g. 40.7128
lonNolongitude, e.g. -74.0060
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, and the description adds context the annotations cannot convey: metered cost ($0.002 USDC on Base via x402), the requirement to call without x_payment first to receive price terms, provider fallback rules, and MET Norway CC BY 4.0 attribution. That is real behavioral and operational disclosure rather than restatement.

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 a single dense sentence but front-loaded with the resource and scope, followed by the useful caveats (not a warning service, pricing). The embedded coordinate example is redundant with the schema and is the one piece of text that does not earn its place.

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, so the description must describe returns, and it does: enumerated forecast fields plus city, state, and forecast office. Cost, payment flow, and provider coverage are all present, leaving nothing an agent needs before calling.

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, and x_payment are already documented with examples and the first-call payment handshake. The description's inline 'lat=40.7128, lon=-74.0060' duplicates the schema examples and adds no new meaning, so the baseline 3 applies.

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?

The description names a specific verb ('forecast'), the exact resource ('a point' via NWS), and the payload shape (current hour plus next 8 periods with temperature, wind, precipitation, short and detailed text, city/state/office). It also explicitly separates itself from a warning service, so an agent can distinguish it from weather_alerts without inspecting either schema.

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 states the geographic split (US points use NWS, other points fall back to MET Norway) and explicitly says 'Forecast, not a warning service', which implicitly routes alert queries to weather_alerts. It does not name the sibling directly or spell out exclusions beyond that, so it falls short of a full when/when-not statement.

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