Skip to main content
Glama
Sign In

Agent Data Tools: Everyday data

by io.github.Nutshell2000
OverviewDiscussionsAdmin

Weather forecast: current weather and 48-hour hourly forecast for any city or coordinates

weather
Read-only

Current weather by city name, or by latitude and longitude, for any place on Earth: temperature in Celsius, conditions (clear, cloudy, rain, snow), precipitation in mm, wind, humidity, cloud cover and air pressure, plus an hourly forecast for up to 48 hours. Data from the Norwegian Meteorological Institute; city names resolve via Wikidata. Use for travel and event planning, logistics, agriculture and any agent that needs the weather. Example: city=London. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

Input Schema

NameRequiredDescriptionDefault
latNoLatitude in decimal degrees, -90 to 90 (with lon, instead of city)
lonNoLongitude in decimal degrees, -180 to 180 (with lat, instead of city)
cityNoCity or place name, e.g. London or Uppsala (used when lat and lon are not given)
hoursNoHours of hourly forecast to return, 1-48 (default 12; 48 covers tomorrow)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
+  "description": "City or place name, e.g. London or Uppsala (used when lat and lon are not given)",
+  "type": "string"
+}
    • changedInput schema / properties / hours / description
      Previous value: -"Hours of hourly forecast to return, 1-48 (default 12)"New value: +"Hours of hourly forecast to return, 1-48 (default 12; 48 covers tomorrow)"
    • changedInput schema / properties / lat / description
      Previous value: -"Latitude in decimal degrees, -90 to 90"New value: +"Latitude in decimal degrees, -90 to 90 (with lon, instead of city)"
    • changedInput schema / properties / lon / description
      Previous value: -"Longitude in decimal degrees, -180 to 180"New value: +"Longitude in decimal degrees, -180 to 180 (with lat, instead of city)"
    • removedInput schema / required
      Removed value: -[
-  "lat",
-  "lon"
-]
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, non-idempotent and non-destructive, and the description adds real value on top: data provenance (Norwegian Meteorological Institute), city resolution via Wikidata, and explicit pricing ($0.002/call via x402 USDC or card key, first 25 free, failed calls free). The line 'each call is charged, so repeats are not free' usefully explains the practical consequence of idempotentHint=false. It does not cover error behavior for unresolvable city names or caching/latency.

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-loaded with the core capability and return fields, then provenance, then cost — a sensible order. The description is dense but nearly every sentence carries information; only the 'Example: city=London' fragment and the 'any agent that needs the weather' clause are low-yield.

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 carries the burden of describing returns and does so by enumerating the weather fields, their units, and the hourly horizon. Combined with 100% schema coverage on inputs, provenance, and pricing, an agent has what it needs to call it correctly; only the exact response shape/ordering is unspecified.

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 the schema already documents lat, lon, city, and hours including ranges and defaults, making 3 the baseline. The description adds only modest semantics beyond that: the Wikidata-based resolution of city names and an example (city=London), while the '48 hours' and Celsius/mm units largely restate schema or return-value detail.

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+resource (current weather plus 48-hour hourly forecast) and enumerates the returned fields: temperature in Celsius, conditions, precipitation in mm, wind, humidity, cloud cover, pressure. It also names the two input modes (city name or lat/lon), which cleanly separates it from siblings like air_quality, sun, or time.

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?

Offers broad use contexts (travel and event planning, logistics, agriculture, 'any agent that needs the weather') but never names an alternative tool or a when-not-to-use condition. The 'any agent that needs the weather' phrasing is close to tautological, so an agent still has to infer that air_quality/sun are different tools for different questions.

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

All Agent Data Tools: Everyday data 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