Skip to main content
Glama

Tollkit

by io.github.UltraStarz
OverviewDiscussionsAdmin

Weather forecast and alerts

weather_forecast
Read-only

Get the weather forecast for any latitude/longitude in the world, or a US street address: the next 7 days in day and night periods (temperature, rain, wind, summary). US locations use the National Weather Service and include any active watches, warnings or advisories; elsewhere the forecast is from MET Norway (in °C and km/h).

$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).

When to use: You need the forecast for a place. Use instead: airport_delays for flight delays; geocode_address when you need coordinates for something else. Parameters: Give lat and lon (anywhere in the world) or address (US street addresses only). periods: 1-14 twelve-hour periods, default 14 (7 days). Returns: forecast[] with name, start and end, temperature, rain, wind and a summary; in the US, active NWS alerts too.

Input Schema

NameRequiredDescriptionDefault
latNoLatitude, e.g. 38.90 (anywhere in the world). Give lat and lon, or a US address.
lonNoLongitude, e.g. -77.04
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.
periodsNoHow many 12-hour periods, 1-14 (default 14, i.e. 7 days).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / periods / description
      Added value: +"How many 12-hour periods, 1-14 (default 14, i.e. 7 days)."
  2. Changed2 schema fields changed
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude, e.g. 38.98 (anywhere in the world). Give lat and lon, or a US address."New value: +"Latitude, e.g. 38.90 (anywhere in the world). Give lat and lon, or a US address."
    • changedInput schema / properties / lon / description
      Previous value: -"Longitude, e.g. -76.49"New value: +"Longitude, e.g. -77.04"
  3. Changed1 schema field changed
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude, e.g. 38.98. Give lat and lon, or address."New value: +"Latitude, e.g. 38.98 (anywhere in the world). Give lat and lon, or a US address."
  4. 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"
-]
  5. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark it read-only and open-world, but the description adds substantial behavioral context: US vs MET Norway data sources, units, NWS alerts, per-call pricing, failed-call cost, quote flow via omitted payment, and the free daily allowance. No annotation contradiction is present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose, then organized into usage, alternatives, parameters, and returns. The pricing and return details earn their place because payment and output behavior are not covered by an output schema.

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?

Given a read-only, open-world forecast tool with no output schema, the description covers data sources, units, alerts, pricing/payment behavior, parameter choices, and return structure. An agent has enough information to invoke 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 description coverage is 100%, so parameter basics are already documented. The description clarifies the lat/lon-or-address choice and summarizes periods as 1-14 twelve-hour periods with default 14, but mostly mirrors the schema rather than adding deep semantics.

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 states a specific verb and resource: get the weather forecast for lat/lon or a US address, including 7-day day/night periods and alerts. It explicitly distinguishes siblings by naming airport_delays and geocode_address as alternatives for different needs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear 'When to use' condition and explicitly names when to use other tools instead: airport_delays for flight delays and geocode_address when coordinates are needed for something else. This leaves little ambiguity about tool selection.

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