Skip to main content
Glama

get_daily_forecast

Read-onlyIdempotent

Retrieve day-by-day weather forecasts for up to 10 days at a latitude/longitude, including highs/lows, precipitation, wind, UV index, and sunrise/sunset in local time.

Instructions

Day-by-day forecast (up to 10 days): highs/lows, precipitation amount and probability, max wind, UV index, and sunrise/sunset, in local time.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "get_daily_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoNumber of forecast days to return (1-10), starting today.
latitudeYesLatitude in decimal degrees (-90 to 90).
longitudeYesLongitude in decimal degrees (-180 to 180).
temperature_unitNoUnit for reported temperatures.celsius

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description contributes one genuine behavioral detail beyond that — results are 'in local time' — but says nothing about data freshness, forecast granularity, or what happens to requests beyond the 10-day cap.

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?

A single dense sentence with the resource and its time horizon front-loaded, followed by the output fields and the timezone qualifier. No filler words and nothing repeated from structured fields unnecessarily.

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?

With an output schema present and 100% parameter coverage, the description need not explain return shapes, and it doesn't waste space doing so. It is nearly complete for a read-only forecast tool; the only notable omission is any hint about location resolution or forecast recency.

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

Parameters4/5

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

Schema description coverage is 100% with well-documented bounds, defaults and an enum for temperature_unit, so the schema carries parameter meaning and baseline is 3. The description reinforces the 10-day ceiling on 'days' and adds the local-time semantics for the returned timestamps, giving it slight value over the schema alone.

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 verb and resource ('Day-by-day forecast') and enumerates exactly what data comes back: highs/lows, precipitation amount and probability, max wind, UV index, sunrise/sunset. The 'daily' framing implicitly separates it from get_hourly_forecast, but the description never names or contrasts 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?

Usage is only implied: the phrase 'up to 10 days' signals a multi-day outlook tool, which is enough for an agent to distinguish it from current conditions. There is no explicit when-to-use/when-not-to-use guidance, no mention of prerequisites such as resolving a location first via geocode_location, and no pointer to alternatives.

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