Skip to main content
Glama

Get hourly forecast

get_hourly_forecast
Read-only

Fetch hour-by-hour US weather forecasts by city, address, or coordinates, including temperature, precipitation probability, and wind for each hour up to 48 hours ahead.

Instructions

Hour-by-hour US weather forecast from the National Weather Service, with temperature, precipitation probability, and wind for each hour.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_hourly_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
hoursNoHow many hours ahead to return.
placeNoUS place name to look up, as "City, ST" (e.g. "Tucson, AZ") or a full street address. Provide either this or latitude+longitude, not both.
latitudeNoLatitude in decimal degrees. Must be paired with longitude.
longitudeNoLongitude in decimal degrees. Must be paired with latitude.
response_formatNomarkdown for a compact human/LLM-readable summary, json for the structured object.markdown

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-lookup behavior are covered. The description adds genuinely useful context beyond that: the data source is the National Weather Service and coverage is limited to US locations, which warns an agent that non-US queries will likely fail. It does not mention rate limits, error behavior for unresolvable places, or the practical time horizon (the schema caps at 48 hours).

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?

A single sentence that front-loads the core purpose and the return contents, with no filler. It is efficient, though the trailing field list is the only detail it carries, leaving no room for routing information.

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?

All five parameters are optional and fully documented in the schema, and there is no output schema, so the description's enumeration of returned fields compensates nicely. The US-only scope is stated, which is the main completeness risk resolved; only error and pagination/limit behavior remain unaddressed.

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%, and every parameter (hours, place, latitude, longitude, response_format) is documented with defaults, ranges, and the either/or constraint. The description adds no parameter-level detail beyond what the schema already provides, so the 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 names a specific verb+resource ('Hour-by-hour US weather forecast') and enumerates the returned fields (temperature, precipitation probability, wind), which clearly separates it from get_current_conditions. It never names get_forecast, so the hourly-vs-daily distinction must be inferred from 'hour-by-hour' rather than stated outright.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling tool is named. An agent must infer that this is the hourly option rather than get_forecast or get_current_conditions, and the description says nothing about how to choose between the place-name and lat/lon input paths (that constraint lives only in the schema).

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