Skip to main content
Glama

Get extended outlook

get_extended_outlook
Read-onlyIdempotent

Get a 16-day daily outlook (snowfall, temperatures, freezing level, maximum gusts and, for the first days, precipitation probability) from EM Snow's self-hosted GFS and ECMWF IFS models. Days 1 to 7 overlap get_forecast; days 8 to 16 are low-confidence trend guidance only.

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": {
      "resort": "<resort>"
    },
    "name": "get_extended_outlook"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
resortYesResort name such as 'Zermatt', or numeric resort id such as 675 (from search_resorts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / resort / description
      Added value: +"Resort name such as 'Zermatt', or numeric resort id such as 675 (from search_resorts)"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: the model provenance and an explicit confidence degradation for days 8-16. It stops short of stating units, timezone, or how missing model data is handled.

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, no filler, with the core capability and field list front-loaded and the caveat about low-confidence days placed where it is read before invocation. Every clause carries information an agent needs.

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 no output schema, the description correctly carries the return-value burden by enumerating the forecast fields, and it sets expectations about reliability. Remaining omissions are units of measure and the forecast timezone, which matter for interpreting values but not for selecting or calling the tool.

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 50%: the resort parameter is documented in-schema while days has only bounds and a default. The description adds useful signal that the outlook is 16 days max and that precipitation probability appears only "for the first days," which hints at how a shortened days value behaves, but it never explains the days parameter directly.

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?

The description names a specific verb and resource ("Get a 16-day daily outlook") and enumerates the returned fields (snowfall, temperatures, freezing level, maximum gusts, precipitation probability) plus the underlying models (GFS, ECMWF IFS). It explicitly positions itself against the sibling get_forecast, so an agent can distinguish the two without opening either schema.

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?

It gives clear context for when this tool is the right choice: extended range, with days 8-16 flagged as low-confidence trend guidance. It also names the overlapping alternative, get_forecast, for days 1-7. The only gap is that "overlap" implies rather than directs which tool to prefer in the shared window.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources