Skip to main content
Glama

Get forecast

get_forecast
Read-only

Fetches multi-day US weather forecasts by place, address, or coordinates from the National Weather Service, returning named periods with temperature, wind, and short conditions.

Instructions

Multi-day US weather forecast from the National Weather Service. Returns named periods (e.g. "Tonight", "Thursday") with temperature, wind, and a short description.

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_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
periodsNoHow many forecast periods to return. Periods are roughly half-days, so 6 is about three days.
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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful context beyond that: the data source (NWS) and the US-only geographic constraint, plus the structure of returned periods. It says nothing about failure behavior for non-US or ambiguous places, which keeps it from a 5.

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?

Two sentences, front-loaded with what the tool is and what it returns. No filler, no repetition of schema or annotation content.

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?

With no output schema, the description carries the return-value burden and does so: named periods with temperature, wind, and a short description. Combined with a fully documented input schema and read-only annotations, an agent has everything needed to call it correctly.

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 coverage is 100%, so the schema already documents all five parameters, including the half-day meaning of `periods` and the markdown/json choice. The description's mention of named periods like 'Tonight' and 'Thursday' reinforces what the periods count refers to but adds little beyond the schema text, 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?

States a specific resource (multi-day US weather forecast) and names the source (National Weather Service), with the return shape spelled out. 'Multi-day' with 'named periods' implicitly separates it from the hourly and current-conditions siblings, but no sibling is named 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?

Usage is implied: use this for multi-day forecasts, and the 'US weather forecast' phrasing implies the geographic limit. There is no explicit when-to-use/when-not or routing to get_hourly_forecast or get_current_conditions when a different time granularity is wanted.

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