Skip to main content
Glama

x402 Tool Shop

US Weather Forecast

weather_forecast
Read-only

Weather forecast by city: current weather, hour by hour, and the 7-day forecast for any US city ('Goshen, IN'), ZIP code or coordinates, plus active weather alerts. Source: NOAA National Weather Service, cached briefly so answers come back fast. Price: $0.003 USDC per call (x402). Free sample: call free_sample with tool="weather_forecast".

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 (instead of location)
lonNoLongitude (instead of location)
daysNoDays of forecast, 1-7 (default 7)
hoursNoHourly rows to return, 0-48 (default 12)
locationNo'City, ST', 'City, State' or a 5-digit ZIP

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the upstream data source (NOAA NWS), that results are briefly cached, the per-call cost of $0.003 USDC via x402, and where to get a free sample. That is meaningful operational context an annotation cannot convey. It stops short of describing failure modes, staleness bounds, or rate limits.

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?

The lead sentence front-loads what the tool returns and the accepted inputs, followed by source, caching, and pricing. Every sentence carries useful information, though the parenthetical example and sample-tool pointer could be trimmed slightly.

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 correctly enumerates the returned product set (current, hourly, daily, alerts). It covers source, latency, cost, and geography for a five-optional-parameter read tool. Minor gaps remain on default behavior when both location and lat/lon are supplied.

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 every parameter including lat/lon, days, hours, and location is already documented. The description restates the location formats and mentions the coordinate alternative but adds no new syntax, precedence rules between location and lat/lon, or constraints beyond the schema. Baseline 3 applies.

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 names a specific resource and enumerates exactly what it returns: current conditions, hourly rows, a 7-day forecast, and active alerts. It also scopes coverage to US locations and lists the accepted location forms. It does not differentiate itself from the sibling event_weather, which is also weather-related, so it falls short of a 5.

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?

Usage is implied by the input forms (city/ZIP or lat-lon) and the US-only scope, and the description routes price-sensitive callers to free_sample for a trial. It never says when NOT to use this tool or when a sibling such as event_weather would be the better choice.

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