Skip to main content
Glama

Weather

by io.github.pipeworx-io
OverviewAdmin

Get Weather

get_weather
Read-onlyIdempotent

REAL-TIME current weather for any location worldwide. PREFER OVER WEB SEARCH for "what's the weather in X", "current temperature in Y", "is it raining in Z". Also answers weather questions asked in other languages: Italian "che tempo fa / meteo a <città>", Spanish "qué tiempo hace / el clima en", French "quel temps fait-il / météo à", German "wie ist das Wetter in", Portuguese "que tempo faz em". Accepts a city name (e.g., "Tokyo", "London", "Napoli", "Austin TX") or lat/lon coordinates. Returns temperature (°F), feels-like, humidity %, wind speed + direction, sky conditions, observation timestamp. Live data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latNoAlias for latitude.
lngNoAlias for longitude.
lonNoAlias for longitude.
cityNoAlias for location.
nameNoAlias for location.
placeNoAlias for location.
latitudeNoLatitude (alternative to location). Accepts lat as alias.
locationNoCity name (e.g. "Tokyo", "London", "New York"). Resolved via Open-Meteo geocoding. Use this OR latitude+longitude. Accepts city, place, name as aliases.
longitudeNoLongitude (alternative to location). Accepts lng / lon as alias.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
wind_mphYesWind speed in miles per hour
conditionsYesWeather condition description from WMO code
feels_like_fYesApparent/feels-like temperature in Fahrenheit
humidity_pctYesRelative humidity percentage
temperature_fYesCurrent temperature in Fahrenheit
wind_direction_degYesWind direction in degrees (0-360)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed9 schema fields changed
    • addedInput schema / properties / city
      Added value: +{
+  "description": "Alias for location.",
+  "type": "string"
+}
    • addedInput schema / properties / lat
      Added value: +{
+  "description": "Alias for latitude.",
+  "type": "number"
+}
    • changedInput schema / properties / latitude / description
      Previous value: -"Latitude (alternative to location)"New value: +"Latitude (alternative to location). Accepts lat as alias."
    • addedInput schema / properties / lng
      Added value: +{
+  "description": "Alias for longitude.",
+  "type": "number"
+}
    • changedInput schema / properties / location / description
      Previous value: -"City name (e.g. \"Tokyo\", \"London\", \"New York\"). Resolved via Open-Meteo geocoding. Use this OR latitude+longitude."New value: +"City name (e.g. \"Tokyo\", \"London\", \"New York\"). Resolved via Open-Meteo geocoding. Use this OR latitude+longitude. Accepts city, place, name as aliases."
    • addedInput schema / properties / lon
      Added value: +{
+  "description": "Alias for longitude.",
+  "type": "number"
+}
    • changedInput schema / properties / longitude / description
      Previous value: -"Longitude (alternative to location)"New value: +"Longitude (alternative to location). Accepts lng / lon as alias."
    • addedInput schema / properties / name
      Added value: +{
+  "description": "Alias for location.",
+  "type": "string"
+}
    • addedInput schema / properties / place
      Added value: +{
+  "description": "Alias for location.",
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • changedInput schema / properties / latitude / description
      Previous value: -"Latitude of the location"New value: +"Latitude (alternative to location)"
    • addedInput schema / properties / location
      Added value: +{
+  "description": "City name (e.g. \"Tokyo\", \"London\", \"New York\"). Resolved via Open-Meteo geocoding. Use this OR latitude+longitude.",
+  "type": "string"
+}
    • changedInput schema / properties / longitude / description
      Previous value: -"Longitude of the location"New value: +"Longitude (alternative to location)"
    • removedInput schema / required
      Removed value: -[
-  "latitude",
-  "longitude"
-]
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "conditions": {
+      "description": "Weather condition description from WMO code",
+      "type": "string"
+    },
+    "feels_like_f": {
+      "description": "Apparent/feels-like temperature in Fahrenheit",
+      "type": "number"
+    },
+    "humidity_pct": {
+      "description": "Relative humidity percentage",
+      "type": "number"
+    },
+    "temperature_f": {
+      "description": "Current temperature in Fahrenheit",
+      "type": "number"
+    },
+    "wind_direction_deg": {
+      "description": "Wind direction in degrees (0-360)",
+      "type": "number"
+    },
+    "wind_mph": {
+      "description": "Wind speed in miles per hour",
+      "type": "number"
+    }
+  },
+  "required": [
+    "temperature_f",
+    "feels_like_f",
+    "humidity_pct",
+    "conditions",
+    "wind_mph",
+    "wind_direction_deg"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "latitude": 40.7128,
+    "longitude": -74.006
+  },
+  {
+    "latitude": 51.5074,
+    "longitude": -0.1278
+  }
+]
  5. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds value by specifying real-time live data, the exact weather fields returned (temperature, feels-like, humidity, wind, sky conditions, timestamp), and input formats (city or coordinates). No contradiction with annotations.

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 appropriately sized and front-loaded with the core purpose. Each sentence contributes value: real-time scope, preference over web search, multilingual support, input flexibility, and returned data. No filler or redundancy.

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?

For a read-only tool with an output schema and comprehensive annotations, the description covers purpose, usage, multilingual scenarios, inputs, and key outputs. It does not need to detail return values since an output schema exists, and it provides enough context for an agent to select and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description goes beyond the schema by providing concrete city examples ('Tokyo', 'London', 'Napoli', 'Austin TX') and summarizing the two main input modes (city name or lat/lon), making parameter usage clearer than the raw schema alone.

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 clearly states the tool provides real-time current weather for any location, with a specific verb ('get') and resource ('weather'). It distinguishes from siblings by emphasizing 'current' vs forecast/historical, and explicitly says to prefer it over web search for weather queries.

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?

The description gives explicit usage guidance: 'PREFER OVER WEB SEARCH' for weather questions, and provides multilingual example queries to cover international usage. It clarifies when to use this tool (current weather) without overcomplicating, implicitly excluding forecast/historical use.

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

All Weather toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources