Skip to main content
Glama

get_hourly_forecast

Read-onlyIdempotent

Retrieve hour-by-hour weather forecasts for a latitude and longitude, including temperature, precipitation, wind, and sky conditions for up to 72 hours.

Instructions

Hour-by-hour forecast (up to 72 hours): temperature, apparent temperature, precipitation probability and amount, wind, and sky description.

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

Input Schema

NameRequiredDescriptionDefault
hoursNoNumber of hours to return (1-72), starting at the current hour.
latitudeYesLatitude in decimal degrees (-90 to 90).
longitudeYesLongitude in decimal degrees (-180 to 180).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds the 72-hour ceiling and the variable set, but omits unit system, timezone basis for the hourly buckets, and data source/freshness — meaningful gaps for a forecast reader.

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?

One front-loaded sentence with the scope and variable list up front and no filler. The variable enumeration earns its place by helping an agent decide between this and a narrower sibling, though it borders on restating the output schema.

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 full parameter descriptions, the description need not explain return values, and its stated scope plus horizon is enough to call the tool correctly. Only units and timezone remain undefined, a minor but real gap.

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%, including the hours range (1-72, default 24, starting at the current hour) and lat/long bounds, so the schema does the heavy lifting. The description only restates the 72-hour maximum and adds no coordinate or time-window semantics beyond it.

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 ('Hour-by-hour forecast') plus the horizon (up to 72 hours) and the returned variables. The 'hour-by-hour' framing implicitly separates it from get_daily_forecast, though it never names that sibling.

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: an agent can infer this is the granular, short-horizon forecast tool, but the description gives no explicit 'use this when / prefer get_daily_forecast when' guidance and no prerequisites (e.g., whether coordinates must be land-based or how a geocode step should precede it).

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