Skip to main content
Glama

Agent Data Tools

by io.github.Nutshell2000
OverviewDiscussionsAdmin

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

weather
Read-only

Weather for any city or point on Earth (city name, or latitude and longitude): current 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.01/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. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: discloses the upstream data source (Norwegian Meteorological Institute), that city names resolve via Wikidata, per-call pricing ($0.01 via x402 USDC or card key, first 25 free, failed calls free), and that repeats are charged — which explains the non-idempotent hint. The 'reads or computes only and changes nothing' line reinforces the read-only profile with concrete detail.

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 capability, then data source, then use cases, then commercial terms — a sensible ordering with no wasted sentences overall. Mild bloat in 'any agent that needs the weather', which restates the obvious, and the pricing clause is dense but earns its place.

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 return-value burden and does so by enumerating the fields and units (Celsius, mm). Remaining gaps are minor: no mention of the response shape (flat vs. nested current/hourly arrays) or what happens when a city name is ambiguous.

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 100%, so lat/lon/city/hours are already documented with ranges and defaults. The description only adds the mutual exclusivity of city vs. lat/lon (already implied by the schema) and an example (city=London); it adds no new syntax, precedence, or ambiguity-resolution guidance for the hours or coordinate parameters.

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?

Names a specific resource and return set: current temperature in Celsius, conditions, precipitation in mm, wind, humidity, cloud cover, pressure, plus up to 48 hours of hourly forecast. It also names both input modes (city name or lat/lon), which cleanly separates it from siblings like sun, moon, time, and geocode.

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?

Explicitly routes usage: 'travel and event planning, logistics, agriculture and any agent that needs the weather', plus a concrete example (city=London). It gives clear context for when to reach for it but never states exclusions or points to a sibling alternative (e.g., geocode for resolving ambiguous place names).

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 toolsInspect
Try in Browser
Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources