Skip to main content
Glama

Daily forecast

get_forecast

Retrieve a 1-16 day daily weather forecast for a city or coordinates, including high/low temperatures, precipitation, wind, and conditions.

Instructions

Get a daily weather forecast (1-16 days) for a location. Specify EITHER a "city" name OR "latitude"+"longitude". Returns per-day high/low temperatures, precipitation total and probability, peak wind, and condition.

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": {
      "days": "<days>",
      "temperature_unit": "<temperature_unit>",
      "wind_speed_unit": "<wind_speed_unit>"
    },
    "name": "get_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoPlace name to geocode, e.g. "Tokyo", "Paris, France", "Austin TX". Provide this OR latitude+longitude.
daysYesNumber of forecast days (1-16).
latitudeNoLatitude in decimal degrees. Provide with longitude to skip geocoding.
longitudeNoLongitude in decimal degrees. Provide with latitude to skip geocoding.
wind_speed_unitYesUnit for wind speed (km/h, m/s, mph, knots).kmh
temperature_unitYesUnit for temperature values.celsius

Output Schema

NameRequiredDescriptionDefault
daysYes
locationYes
wind_speed_unitYes
temperature_unitYes

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?

With no annotations at all, the description must carry the behavioral burden, and it does cover the read nature implicitly and the return payload explicitly. It does not say what happens if both city and coordinates are supplied, what errors look like for unknown places, or any rate/availability constraints. Adequate but not rich.

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?

Three tight sentences, front-loaded with purpose and then inputs. The final sentence enumerating return fields is largely redundant given a declared output schema, which is the only wasted clause.

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?

For a read-only forecast tool with an output schema and full parameter descriptions, nothing essential is missing: purpose, horizon, location modes, and returned values are all covered.

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 coverage is 100%, so the baseline is 3, but the description adds a real constraint the schema does not encode: the inputs are mutually exclusive location strategies (city OR latitude+longitude). That is meaningful meaning beyond the schema, which merely lists both without a oneOf.

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 ("Get a daily weather forecast") plus the horizon (1-16 days) and the location modes, which implicitly separates it from get_current_weather. It never names the sibling explicitly, so an agent must infer that this is the multi-day tool rather than the current-conditions one.

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 EITHER/OR location guidance is genuinely useful invocation guidance, but it addresses how to call the tool, not when to choose it over get_current_weather or whether to call geocode_location first. Usage context is implied rather than stated, and no exclusions are given.

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

Deploy Server

Other Tools