Skip to main content
Glama

lookup_weather

Read-only

Retrieves comprehensive weather data including current conditions, hourly, and daily forecasts.

Specific Data Available: Temperature (Current, Feels Like, Max/Min, Heat Index), Wind (Speed, Gusts, Direction), Celestial Events (Sunrise/Sunset, Moon Phase), Precipitation (Type, Probability, Quantity/QPF), Atmospheric Conditions (UV Index, Humidity, Cloud Cover, Thunderstorm Probability), and Geocoded Location Address.

Location & Location Rules (CRITICAL):

The location for which weather data is requested is specified using the location field. This field is a 'oneof' structure, meaning you MUST provide a value for ONLY ONE of the three location sub-fields below to ensure an accurate weather data lookup.

  1. Geographic Coordinates (lat_lng)

    • Use it when you are provided with exact lat/lng coordinates.

    • Example: {"location": {"lat_lng": {"latitude": 34.0522, "longitude": -118.2437}}} // Los Angeles

  2. Place ID (place_id)

    • An unambiguous string identifier (Google Maps Place ID).

    • The place_id can be fetched from the search_places tool.

    • Example: {"location": {"place_id": "ChIJLU7jZClu5kcR4PcOOO6p3I0"}} // Eiffel Tower

  3. Address String (address)

    • A free-form string that requires specificity for geocoding.

    • City & Region: Always include region/country (e.g., "London, UK", not "London").

    • Street Address: Provide the full address (e.g., "1600 Pennsylvania Ave NW, Washington, DC").

    • Postal/Zip Codes: MUST be accompanied by a country name (e.g., "90210, USA", NOT "90210").

    • Example: {"location": {"address": "1600 Pennsylvania Ave NW, Washington, DC"}}

Usage Modes:

  • Current Weather: Provide location only. Do not specify date and hour.

  • Hourly Forecast: Provide location, date, and hour (0-23). Use for specific times (e.g., "at 5 PM") or terms like "next few hours" or "later today". If the user specifies minute, round down to the nearest hour. Hourly forecast beyond 120 hours from now is not supported. Historical hourly weather is supported up to 24 hours in the past.

  • Daily Forecast: Provide location and date. Do not specify hour. Use for general day requests (e.g., "weather for tomorrow", "weather on Friday", "weather on 12/25"). If today's date is not in the context, you should clarify it with the user. Daily forecast beyond 10 days including today is not supported. Historical weather is not supported.

Parameter Constraints:

  • Timezones: All date and hour inputs must be relative to the location's local time zone, not the user's time zone.

  • Date Format: Inputs must be separated into {year, month, day} integers.

  • Units: Defaults to METRIC. Set units_system to IMPERIAL for Fahrenheit/Miles if the user implies US standards or explicitly requests it.

  • The grounded output must be attributed to the source using the information from the attribution field when available.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoOptional. The date of the required weather information. Note: This date is relative to the local timezone of the location specified in the location field. The date must be between 24 hours in the past and the next 10 days.
hourNoOptional. The hour of the requested weather information, in 24-hour format (0-23). This value is relative to the local timezone of the location specified in the location field. Hourly forecast beyond 120 hours from now is not supported. Historical hourly weather is supported up to 24 hours in the past.
locationYesRequired. The location to get the weather conditions for.
unitsSystemNoOptional. The units system to use for the returned weather conditions. If not provided, the returned weather conditions will be in the metric system (default = METRIC).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
windNoThe wind conditions
uvIndexNoThe maximum ultraviolet (UV) index. define optional because it is not always available
heatIndexNoThe hourly heat index temperature.
sunEventsNoThe events related to the sun (e.g. sunrise, sunset).
cloudCoverNoThe percentage of the sky covered by clouds (values from 0 to 100). define optional because it is not always available
moonEventsNoThe events related to the moon (e.g. moonrise, moonset).
airPressureNoThe hourly air pressure conditions.
attributionNoRequired attribution to show with the weather.
temperatureNoThe hourly temperature
maxHeatIndexNoThe maximum heat index temperature throughout the day.
precipitationNoThe precipitation probability and amount of precipitation accumulated
maxTemperatureNoThe maximum (high) temperature throughout the day.
minTemperatureNoThe minimum (low) temperature throughout the day.
relativeHumidityNoThe percent of relative humidity (values from 0 to 100). define optional because it is not always available
returnedLocationNoRequired. The location where the weather information is returned. This location is identical to the location in the request, but can be different from it if the requested location is a free text address that looks up to a coarse location (e.g. "Mountain View, CA").
weatherConditionNoThe weather condition
feelsLikeTemperatureNoThe hourly measure of how the temperature feels like.
feelsLikeMaxTemperatureNoThe maximum (high) feels-like temperature throughout the day.
feelsLikeMinTemperatureNoThe minimum (low) feels-like temperature throughout the day.
thunderstormProbabilityNoThe thunderstorm probability (values from 0 to 100). define optional because it is not always available

TDQS

A5/5.0
Behavior5/5

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

While annotations already indicate readOnlyHint=true and destructiveHint=false, the description adds crucial behavioral constraints beyond those: timezone handling ('relative to the location's local time zone'), forecast limits ('Hourly forecast beyond 120 hours... not supported', 'Daily forecast beyond 10 days... not supported'), and the requirement to attribute output using the attribution field. These details meaningfully enrich the agent's understanding of edge cases and limitations.

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 long but well-structured with bold headers, bullets, and code examples. Every section addresses a distinct aspect (data available, location rules, usage modes, constraints) without redundancy. The core purpose is front-loaded in the first sentence, and the formatting makes complex information easily scannable.

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 the tool's complexity (multiple modes, three location types, timezone handling) and the presence of an output schema, the description covers all essential contextual aspects: available data, location selection rules, usage mode conditions, forecast limits, and attribution. It addresses practical edge cases like rounding minutes down to the nearest hour and clarifying today's date when absent, making the tool complete for an agent to invoke correctly.

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

Parameters5/5

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

Even though schema documentation covers all 4 parameters, the description adds significant semantic value: it explains the 'oneof' requirement for location sub-fields with concrete JSON examples, specifies address formatting rules (city with region, full street address, postal code requiring country), and clarifies unit defaulting ('Defaults to METRIC. Set units_system to IMPERIAL...'). This goes far beyond the schema's field-level definitions.

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 opens with 'Retrieves comprehensive weather data including current conditions, hourly, and daily forecasts,' which clearly states a specific action (retrieves) and resource (weather data), and explicitly distinguishes the three forecast modes. This differentiates lookup_weather from sibling tools like compute_routes and search_places, which address different domains.

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 provides highly explicit guidance on when to use each mode: 'Current Weather: Provide location only. Do not specify date and hour.' 'Hourly Forecast: Provide location, date, and hour...' It also gives decision rules for ambiguous terms ('next few hours', 'later today'), and instructs to clarify when today's date is not in context. This exceeds simple context by providing precise usage criteria for each scenario.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0
Disambiguation5/5

Each tool has a distinctly different purpose: compute_routes for travel directions, lookup_weather for meteorological data, search_places for free-text place discovery, and resolve_maps_urls/resolve_names for batch converting specific inputs (URLs or exact names) into canonical place IDs. There is no overlap in function that would cause an agent to select the wrong tool.

Naming Consistency4/5

All tools follow a verb_noun snake_case pattern (compute_routes, lookup_weather, search_places, resolve_names, resolve_maps_urls). The use of 'resolve' for two tools is slightly redundant but each targets a distinct input type (names vs. URLs), so the pattern remains predictable and clear.

Tool Count5/5

With five tools, the server is well-scoped for a Google Maps integration. It covers the essential capabilities (routing, weather, place search, and ID resolution) without unnecessary bloat, falling comfortably within the ideal 3-15 tool range.

Completeness4/5

The tool surface covers core map-related tasks: route calculation, weather, place searching, and canonical place ID resolution from both URLs and named locations. A potential gap is lack of a dedicated reverse geocoding tool (lat/lng → address), but lookup_weather's geocoded output partially covers this, and search_places can handle address-like queries. Overall, the domain is well covered with only minor omissions.

Resources