Skip to main content
Glama

NS Pros MCP Gateway

google-maps__lookup_weather

Retrieves comprehensive environmental intelligence for a location, including Weather, Air Quality (AQI & pollutants), and Pollen (tree, grass, weed, and plant species allergen levels): current conditions, hourly forecasts/history, and daily forecasts for Weather and Air Quality; Pollen is a daily forecast only (today through +4 days, no hourly or past data). Available Environmental Domains & Capabilities (capabilities: WEATHER, AIR_QUALITY, POLLEN — CRITICAL):

  • **Mandatory Explici

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": {
      "location": "<location>"
    },
    "name": "google-maps__lookup_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoOptional. Specifies the date of the requested environmental information, relative to the local timezone of the location specified in the `location` field. Supported date ranges depend on the requested capabilities: - `WEATHER`: up to 24 hours in the past (when `hour` is also set) and up to 10 days (240 hours) in the future (today through +9 days for daily forecasts). - `AIR_QUALITY`: up to 30 days (720 hours) in the past and up to 4 days (96 hours) in the future. - `POLLEN`: today through +4 days (up to 5 days including today; historical dates are not supported).
hourNoOptional. Specifies the hour of the requested environmental information, in 24-hour format (0-23), relative to the local timezone of the location specified in the `location` field. Requires `date` to be specified. Supported hourly ranges depend on the requested capabilities: - `WEATHER`: up to 24 hours in the past and up to 240 hours (10 days) in the future. - `AIR_QUALITY`: up to 30 days (720 hours) in the past and up to 4 days (96 hours) in the future. - `POLLEN`: returns daily forecasts only; `hour` is ignored for pollen.
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).
capabilitiesNoOptional. The environmental capabilities to include in the response.
languageCodeNoOptional. The BCP-47 language code for localized text in the response (e.g. "en", "ja", "fr-CA"). Defaults to "en" if not specified.
weatherOptionsNoOptional. Options specific to weather requests. `weather_options.units_system` is supported in tandem with top-level `units_system` (tag 4) to preserve backwards compatibility for existing callers; returns INVALID_ARGUMENT if both specify conflicting unit systems. Ignored if `WEATHER` is not requested in `capabilities`.
airQualityOptionsNoOptional. Options specific to air quality requests. Ignored if `AIR_QUALITY` is not requested in `capabilities`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose some real behavior: Pollen ignores `hour`, and per-domain history/forecast horizons differ. It says nothing about permissions, quotas, response size, or error conditions, and the truncated 'CRITICAL' capabilities warning leaves an unknown behavioral requirement unexplained.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose sentence is front-loaded and dense with genuinely useful detail, but the body relies on bold-header bullet scaffolding and ends in a dangling fragment ('**Mandatory Explici'), which is wasted space rather than concise structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 8-parameter tool with full schema coverage and no output schema, the schema does most of the work and the description covers domains and time ranges adequately. However, the cut-off mandatory-guidance section is precisely the part an agent needs in order to call this correctly, leaving a gap that annotations do not fill.

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 explains `date`, `hour`, `location`, `unitsSystem`, and the options objects in detail. The description adds only the framing that `capabilities` is critical, and even that sentence is truncated, so it contributes little beyond the structured data. 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?

Opens with a specific verb and resource: 'Retrieves comprehensive environmental intelligence for a location,' then enumerates the three domains (Weather, Air Quality, Pollen) with their sub-capabilities. The scope is unmistakable and distinguishable from sibling maps tools like search_places or compute_routes, though it never names a sibling explicitly.

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 only usable guidance that survives is a constraint on Pollen ('daily forecast only, today through +4 days, no hourly or past data'). The promised 'Mandatory Explici...' section that was flagged as CRITICAL is cut off mid-word, so the primary when-to-use / when-not-to-use directive is never delivered.

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.