Skip to main content
Glama
Sign In

SnowSure — Snow & Ski

by ai.snowsure
OverviewDiscussionsAdmin

Subscribe to snow alerts

subscribe_alerts

Subscribe the signed-in user to snow alerts. Requires a SnowSure user access token (OAuth). type: 'powder' (OBSERVED fresh snow >= thresholdCm in 24h), 'forecast' (the forecast total over windowDays clears thresholdCm — 14 days with Pro or on a resort in My Mountains, 7 otherwise), 'trip' (a Powder Trip — a storm inside 14 days with a curated stay to book — at a resort you name, or on a pass via scope 'pass:ikon-pass' / 'pass:epic-pass' / 'pass:mountain-collective'; scope 'any' is not accepted for trips), 'opening' (resort opens for the season), or 'bluebird' (powder day then clear skies).

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": {
      "type": "<type>"
    },
    "name": "subscribe_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesAlert type
scopeNoResort slug, or 'any' for all resorts (default 'any'); for type 'trip' also 'pass:<pass-id>' (pass:ikon-pass, pass:epic-pass, pass:mountain-collective)
channelNoDelivery channel (default email)
windowDaysNoforecast alerts only: scan the next N days of forecast (1–14, default 14; resorts outside My Mountains read 7 without Pro)
thresholdCmNoSnow threshold in cm — fresh-snow for powder (default 15), forecast total over windowDays for forecast (default 30)

Output Schema

NameRequiredDescriptionDefault
markdownNoHuman-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / windowDays / description
      Previous value: -"forecast alerts only: scan the next N days of forecast (1–14, default 14; resorts outside your favourites read 7 without Pro)"New value: +"forecast alerts only: scan the next N days of forecast (1–14, default 14; resorts outside My Mountains read 7 without Pro)"
  2. Changed2 schema fields changed
    • changedInput schema / properties / thresholdCm / description
      Previous value: -"Snow threshold in cm — fresh-snow for powder (default 15), 14-day forecast total for forecast (default 30)"New value: +"Snow threshold in cm — fresh-snow for powder (default 15), forecast total over windowDays for forecast (default 30)"
    • changedInput schema / properties / windowDays / description
      Previous value: -"forecast alerts only: scan the next N days of forecast (1–14, default 14)"New value: +"forecast alerts only: scan the next N days of forecast (1–14, default 14; resorts outside your favourites read 7 without Pro)"
  3. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "powder",
-  "opening",
-  "bluebird",
-  "forecast",
-  "trip"
-]New value: +[
+  "powder",
+  "opening",
+  "bluebird",
+  "forecast",
+  "trip",
+  "chance"
+]
  4. Changed2 schema fields changed
    • changedInput schema / properties / scope / description
      Previous value: -"Resort slug, or 'any' for all resorts (default 'any')"New value: +"Resort slug, or 'any' for all resorts (default 'any'); for type 'trip' also 'pass:<pass-id>' (pass:ikon-pass, pass:epic-pass, pass:mountain-collective)"
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "powder",
-  "opening",
-  "bluebird",
-  "forecast"
-]New value: +[
+  "powder",
+  "opening",
+  "bluebird",
+  "forecast",
+  "trip"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "powder",
-  "opening",
-  "bluebird",
-  "digest",
-  "forecast"
-]New value: +[
+  "powder",
+  "opening",
+  "bluebird",
+  "forecast"
+]
  6. Changed2 schema fields changed
    • changedOutput schema / properties / markdown / description
      Previous value: -"Human-readable markdown summary of the tool result."New value: +"Human-readable markdown summary of the tool result (may be omitted when structuredContent carries a typed payload; content[0].text always has the prose)."
    • removedOutput schema / required
      Removed value: -[
-  "markdown"
-]
  7. Changed3 schema fields changed
    • changedInput schema / properties / thresholdCm / description
      Previous value: -"Fresh-snow threshold in cm for powder alerts (default 15)"New value: +"Snow threshold in cm — fresh-snow for powder (default 15), 14-day forecast total for forecast (default 30)"
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "powder",
-  "opening",
-  "bluebird",
-  "digest"
-]New value: +[
+  "powder",
+  "opening",
+  "bluebird",
+  "digest",
+  "forecast"
+]
    • addedInput schema / properties / windowDays
      Added value: +{
+  "description": "forecast alerts only: scan the next N days of forecast (1–14, default 14)",
+  "type": "number"
+}
  8. Changed1 schema field changed
    • changedInput schema / properties / type / enum
      Previous value: -[
-  "powder",
-  "opening",
-  "bluebird"
-]New value: +[
+  "powder",
+  "opening",
+  "bluebird",
+  "digest"
+]
  9. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, non-destructive behavior. The description adds a real behavioral fact beyond them: it requires a SnowSure OAuth access token, which the agent needs before calling. It stops short of describing duplicate-subscription behavior or rate limits, so it is not a full 5.

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?

The core action is front-loaded and the second half is dense but earns its place by disambiguating the alert types. It is a run-on sentence heavy with em-dashes that would read better as a structured list, costing a point on structure.

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, return values need not be explained. The description covers auth, type semantics, and the trip/scope restriction well, but leaves the 'chance' type and duplicate-subscription behavior undocumented.

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 materially enriches the 'type' enum by explaining each value's trigger semantics (OBSERVED fresh snow, forecast totals, Powder Trip, opening, bluebird) and adds the constraint that scope 'any' is rejected for trips. It omits the 'chance' enum value present in the schema, so it does not fully cover the parameter space.

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 opens with a specific verb+resource ('Subscribe the signed-in user to snow alerts') that cleanly distinguishes it from the list_alerts and unsubscribe_alerts siblings. The 'signed-in user' scoping makes the target of the mutation unambiguous.

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 implied by the verb (subscribing), but there is no explicit when-to-use guidance and no reference to the alternatives (list_alerts, unsubscribe_alerts). It never states conditions like 'use unsubscribe_alerts to stop receiving' or prerequisites for creating a subscription.

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

All SnowSure — Snow & Ski toolsInspect
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.

Resources