geosphere-mcp-server

get_hourly_forecast

Retrieve an hour-by-hour forecast for a coordinate in Austria or the Alpine region, with optional start time and up to 60 hours. Use it to plan around localized hourly conditions.

Instructions

Get an hour-by-hour weather forecast for a location.

High-resolution GeoSphere AROME data (1 km, up to ~60 h). Each hour's
condition is GeoSphere's own weather symbol; the precipitation chance is an
estimate derived from C-LAEF ensemble percentiles (0/30/70/95 %), not a
probability GeoSphere publishes. Serves Austria and the Alpine region only;
a point outside that grid returns an out-of-coverage notice.

Args:
    latitude: Decimal latitude (e.g. 48.2208 for Vienna). Geocode city
        names to coordinates yourself.
    longitude: Decimal longitude (e.g. 16.3738 for Vienna).
    hours: Number of forecast hours (default 24, clamped to 1–60).
    start: Optional ISO 8601 start time (e.g. "2026-07-22T15:00"); the
        forecast begins at/after this instant instead of now. Without
        an offset it is Vienna local time, like the times in the output.

Input Schema

Name	Required	Description	Default
`hours`	No
`start`	No
`latitude`	Yes
`longitude`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 31, 2026

TDQS

A4.3/5.0

Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose valuable non-obvious traits: the precipitation chance is a C-LAEF ensemble-derived estimate (0/30/70/95 %) rather than a published probability, coverage is limited and out-of-grid points yield a notice, and times are Vienna local. It does not describe errors, ordering, or rate behavior, so it is solid but not exhaustive for an annotation-free tool.

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?

Front-loaded with the one-line purpose, then a compact paragraph of caveats, then per-argument notes in a conventional Args block. The provenance paragraph is long but each sentence (resolution, symbol source, precipitation derivation, coverage, timezone) carries information an agent cannot get from the schema.

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 4-parameter read tool with an output schema (so return fields needn't be explained), the description covers the remaining unknowns: data source and resolution, forecast horizon, geographic coverage and failure mode, timezone convention, and clamping. Nothing material is left for the agent to guess.

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

Parameters5/5

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

Schema description coverage is 0%, and the description fully compensates: it explains latitude/longitude with concrete Vienna examples, hours with its default and 1–60 clamp, and start as an optional ISO 8601 instant with the crucial detail that a missing offset means Vienna local time matching output times.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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 weather forecast for a location') and immediately narrows the product: GeoSphere AROME at 1 km resolution, up to ~60 h. Combined with sibling names like get_current_weather, an agent can tell this is the multi-hour forecast tool rather than a current-conditions or air-quality tool.

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

Usage Guidelines4/5

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

Gives the operative preconditions for calling it: coordinates must be supplied by the caller ('Geocode city names to coordinates yourself') and the point must fall in the Austria/Alpine grid or an out-of-coverage notice is returned. It does not explicitly say 'use get_current_weather instead when you only need present conditions', so routing to siblings is left implied by names.

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

Deploy Server