Skip to main content
Glama

Current weather

get_current_weather

Look up current weather for a city or coordinates and get temperature, feels-like, humidity, precipitation, wind, and conditions in your chosen units.

Instructions

Get current weather conditions for a location. Specify EITHER a "city" name (it will be geocoded automatically) OR explicit "latitude" and "longitude". Returns temperature, "feels like", humidity, precipitation, wind, and a human-readable condition.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "temperature_unit": "<temperature_unit>",
      "wind_speed_unit": "<wind_speed_unit>"
    },
    "name": "get_current_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoPlace name to geocode, e.g. "Tokyo", "Paris, France", "Austin TX". Provide this OR latitude+longitude.
latitudeNoLatitude in decimal degrees. Provide with longitude to skip geocoding.
longitudeNoLongitude in decimal degrees. Provide with latitude to skip geocoding.
wind_speed_unitYesUnit for wind speed (km/h, m/s, mph, knots).kmh
temperature_unitYesUnit for temperature values.celsius

Output Schema

NameRequiredDescriptionDefault
is_dayYes
locationYes
conditionYesHuman-readable weather description (from WMO code).
wind_speedYes
observed_atYesISO-8601 timestamp of the observation (local time).
temperatureYes
weather_codeYes
precipitationYes
wind_directionYesDegrees, meteorological (0 = from North).
wind_speed_unitYes
temperature_unitYes
relative_humidityYesPercent, 0-100.
apparent_temperatureYes"Feels like" temperature.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose one non-obvious behavior: city names are geocoded automatically. It does not cover what happens on ambiguous or unresolvable place names, whether supplying both city and coordinates is rejected, or any rate/error behavior. The read-only nature is implied by "Get" but never stated.

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?

Three tight sentences with the core action front-loaded and the input-mode rule immediately after. The final sentence listing return fields partially duplicates the output schema, so it is not entirely free of redundancy, but nothing is padded.

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?

For a five-parameter read tool with a fully documented schema and an output schema, this is close to sufficient: purpose, input modes, and geocoding behavior are all covered. The remaining gap is failure handling for bad or ambiguous locations and for conflicting inputs, which an agent would need before relying on it.

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 all five parameters are already documented with units, ranges, and examples. The description reinforces the mutually exclusive city-versus-coordinates pattern, which is mildly useful, but adds no syntax, format, or default information beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 current weather conditions") and enumerates the returned fields, so an agent knows exactly what it produces. It does not name or contrast with the sibling get_forecast, so the current-versus-forecast distinction is only implied by the word "current".

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?

The description gives useful input-mode guidance ("Specify EITHER a city name ... OR explicit latitude and longitude"), but that is parameter routing, not tool selection. It never says when to prefer this over get_forecast or when to call geocode_location first, leaving the sibling decision to inference.

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

Deploy Server

Other Tools