PeakCam Snow

Snow history

get_snow_history

Read-onlyIdempotent

Daily snow depth, snow water equivalent, precipitation accumulation and temperatures for the last 1–30 days at the resort's station (SNOTEL where there is one, Open-Meteo model otherwise), newest first. Use it for "how has the base changed this week" questions. Pass season (2024-25, or current) for a whole season's daily depth and new-snow rows instead of the last N days; get_season_stats summarises a season.

Input Schema

Name	Required	Description
`days`	No	Days back, 1–30. Ignored when `season` is set.
`slug`	Yes	PeakCam resort slug, lowercase kebab-case, e.g. `breckenridge` or `ski-portillo`. Get it from search_resorts.
`season`	No	A season label (`2024-25` for the Northern water year, `2026` for an Andes resort) or `current`: returns every daily row of that season, oldest first, with daily new snow.

Output Schema

Name	Required	Description
`days`	Yes
`name`	Yes
`rows`	Yes
`slug`	Yes
`count`	Yes
`season`	Yes	The season label when `season` was asked for; null for a last-N-days read.
`source`	Yes
`station`	Yes
`generatedAt`	Yes	ISO-8601 UTC instant the result was generated.
`canonicalUrl`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 20, 2026

changedInput schema / properties / days / description

Previous value: -"Days back, 1–30."New value: +"Days back, 1–30. Ignored when `season` is set."

addedInput schema / properties / season

Added value: +{
+  "description": "A season label (`2024-25` for the Northern water year, `2026` for an Andes resort) or `current`: returns every daily row of that season, oldest first, with daily new snow.",
+  "pattern": "^(current|\\d{4}(-\\d{2})?)$",
+  "type": "string"
+}

addedOutput schema / properties / rows / items / properties / newSnowIn

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Daily new snow (positive depth change), season reads only."
+}

addedOutput schema / properties / season

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "The season label when `season` was asked for; null for a last-N-days read."
+}

changedOutput schema / required

Previous value: -[
-  "slug",
-  "name",
-  "canonicalUrl",
-  "source",
-  "station",
-  "days",
-  "count",
-  "rows",
-  "generatedAt"
-]New value: +[
+  "slug",
+  "name",
+  "canonicalUrl",
+  "source",
+  "station",
+  "days",
+  "season",
+  "count",
+  "rows",
+  "generatedAt"
+]

First observedOct 18, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the description's added value is the station provenance (SNOTEL where available, otherwise Open-Meteo model) and the ordering difference between the days view (newest first) and the season view (oldest first). These are real behavioral details not derivable from the annotations.

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?

Dense but well-structured: the payload is front-loaded, then the usage case, then the parameter/sibling routing. Every sentence earns its place, though the parenthetical source detail and the routing clause make it slightly long for the amount of schema support available.

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?

With an output schema present (so return values need no prose) and annotations covering the safety profile, the description supplies the remaining essentials: what data, from which source, in what order, and how the season path differs. Nothing an agent needs to call it correctly is missing.

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 goes further by explaining the days/season interaction (season returns every daily row of the season with new snow, superseding the last-N-days window) rather than merely restating the schema.

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 resource (daily snow depth, SWE, precipitation, temperatures) with explicit scope (last 1–30 days at the resort's station), data provenance (SNOTEL vs Open-Meteo model), and ordering (newest first). An agent can distinguish this from get_season_stats and get_forecast without opening any 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?

Gives a concrete when-to-use case ("how has the base changed this week") and routes the agent to the right sibling for season summaries (get_season_stats) and to the `season` parameter for whole-season rows. It stops short of an explicit when-not (e.g. vs. get_forecast for future snow), so it is clear but not fully closed.

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

All PeakCam Snow tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.