Skip to main content
Glama

Tollkit

by io.github.UltraStarz
OverviewDiscussionsAdmin

US weather forecast and alerts

weather_forecast
Read-only

Get the US National Weather Service forecast for a US street address or a latitude/longitude: the next 7 days in day and night periods (temperature, chance of rain, wind, summary) plus any active watches, warnings or advisories. United States and territories only.

$0.002 USDC per call over x402. Failed calls cost nothing. Call without payment to get a quote. The first 3 calls a day through this tool server are free (no wallet needed).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoLatitude, e.g. 38.98. Give lat and lon, or address.
lonNoLongitude, e.g. -76.49
addressNoUS street address instead of lat/lon, e.g. "1600 Pennsylvania Ave NW, Washington, DC".
paymentNoBase64 x402 payment payload. Omit it to receive a quote; sign that and call again.
periodsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / address
      Added value: +{
+  "description": "US street address instead of lat/lon, e.g. \"1600 Pennsylvania Ave NW, Washington, DC\".",
+  "type": "string"
+}
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude, e.g. 38.98"New value: +"Latitude, e.g. 38.98. Give lat and lon, or address."
    • removedInput schema / required
      Removed value: -[
-  "lat",
-  "lon"
-]
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnly and openWorld, so the description's addition of the pricing model ($0.002 USDC per call over x402), the zero-cost-on-failure behavior, the quote handshake, and the free daily tier is genuinely valuable behavioral context—especially the fact that a call must be made without `payment` first to obtain a signable quote. It stops short of stating rate limits or timeout/retry behavior, keeping it from a 5.

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-loads the core purpose and return shape, then isolates the payment mechanics in their own short paragraph. Every sentence is actionable, though the pricing tier wording is slightly dense and could be trimmed.

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?

With no output schema, the description carries the return-value burden and fully discharges it by describing the period structure and the alert payload. Combined with the payment/auth flow and geographic scope, an agent has everything needed to call it correctly.

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 80%, so the schema already documents lat, lon, address, and payment. The description reinforces the address-or-lat/lon duality but never mentions the `periods` parameter by name; it only implies a default of 7 days against a schema max of 14. Baseline 3 is appropriate given the schema does most of the work.

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 ('Get the US National Weather Service forecast') narrowed to a US address or lat/lon, and enumerates exactly what comes back: 7 days of day/night periods with temperature, rain chance, wind, summary, plus active watches/warnings/advisories. No sibling tool covers weather, and this is unmistakably distinct from the geocode/airport token tooling.

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?

Gives clear operational context: United States and territories only, and the payment flow (call without `payment` to get a quote first, 3 free calls/day). It does not name alternatives, but no sibling performs forecasting, so there is no real routing decision to spell out. The one gap is that exclusions beyond geography aren't stated.

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

All Tollkit toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources