Skip to main content
Glama

ML/AI trends

get_ml_trends
Read-onlyIdempotent

Fetch machine-learning trend datasets from SnowSure's API for powder-day rankings, bluebird predictions, model accuracy, and extended outlook. Use with dataset=catalog to explore endpoints.

Instructions

Fetch SnowSure-unique ML/AI trend datasets from the public REST API. Use for powder-day leaders, bluebird-day leaders, bluebird predictions, improving/stable/declining score pulse, per-model accuracy weights, daily SnowSure score component history, ML extended outlook (days 8–14), global forecast trust, and powder/bluebird event logs. Start with dataset=catalog. Prefer get_insights for narrative intelligence cards; use this for raw rankings and time series.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNoLookback days for score_components (default 30, max 365).
slugNoResort slug — required for score_components, vs_last_year, and season_stats; optional for extended_outlook (per-resort).
limitNoMax rows for leaderboards or snow_events (default 25, max 100).
minCmNoMinimum ML days 8–14 snow (cm) when dataset=extended_outlook leaderboard (default 0).
statsNoWhen dataset=snow_events, return season aggregates instead of events.
resortNoResort slug filter when dataset=snow_events.
datasetYesTrend dataset to fetch. catalog lists all endpoints; powder_days / bluebird_days = season leaderboards; score_components needs slug.
openOnlyNoWhen dataset=extended_outlook, filter to open resorts only (default true).
eventTypeNoFilter snow_events by event type.
minSpreadNoMinimum 14d model spread (cm) when dataset=forecast_disagreement (default 5).

Output Schema

TableJSON 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).
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the description is not required to repeat safety traits. It adds value by specifying the data source (public REST API) and listing the datasets, which gives insight into what the tool accesses. No contradiction with annotations.

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?

The description is concise: two sentences that front-load purpose, list datasets, and provide usage guidance. No filler words; every sentence adds value.

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?

Given the tool has 10 parameters and an output schema, the description provides an effective overview of available datasets and a starting point. It differentiates from a major sibling tool. It doesn't need to detail every parameter since the schema covers it. A minor gap might be not explaining the behavior when no parameters are specified aside from dataset, but the schema and annotation imply safe read. Overall adequate.

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 baseline is 3. The description adds organizational guidance (start with catalog, slug required for certain datasets) that enhances the schema descriptions, earning an extra point.

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 clearly states the specific verb 'Fetch' and the resource 'SnowSure-unique ML/AI trend datasets'. It distinguishes itself from sibling tool 'get_insights' by noting its use for raw rankings and time series, and advises starting with dataset=catalog.

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

Usage Guidelines5/5

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

Explicitly provides when to use this tool (for raw rankings and time series) and when not to (prefer get_insights for narrative cards). Also recommends starting with dataset=catalog, giving clear usage context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mikeslone/snowsure-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server