PeakCam Snow: tool descriptions scored io.peakcam/snow

tools/list taken: 2026-11-02 (UTC)
From: Official MCP Registry
Connected to: https://www.peakcam.io/api/mcp
Homepage: www.peakcam.io/connect
Repository: github.com/jaredschueler07/peakcam
Scoring rules: v2
Removal: support@forecall.dev

Scores, issues and names only

This page shows how PeakCam Snow (io.peakcam/snow)'s tool descriptions scored, the issues found and the names of its tools and parameters. The descriptions are the server's own: read them where the copy came from.

Forecall asked the URL this server lists in the official MCP Registry for its tools/list once, on the date above, without calling any tool. The server may have changed since.

servers/io.peakcam/snow

Average score: 70.6 / 100Clear
Tools: 21
Near-identical descriptions: 0

Across the server

No server-wide issues.

Tools

get_alert_options

57 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 0 / 10

Minor
No `required` list, so every argument is optional.no_required

get_opening_dates

57 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
No `required` list, so every argument is optional.no_required

get_leaderboard

60 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

get_percent_of_normal

62 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context
Minor
No `required` list, so every argument is optional.no_required

list_regions

62 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 25 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

get_resort_profile

63 / 100Cloudy

Purpose: 20 / 20
When to use: 0 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

compare_models

65 / 100Cloudy

Purpose: 17 / 20
When to use: 0 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

Major
Says nothing about when to use it, or when not to.no_usage_context

compare_resorts

67 / 100Cloudy

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 23 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 0 / 10

No issues.

search_resorts

68 / 100Cloudy

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 5 / 10

Minor
The description mentions none of its 3 or more arguments.params_not_in_description

get_stations

70 / 100Clear

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

No issues.

find_powder

73 / 100Clear

Purpose: 20 / 20
When to use: 5 / 20
Arguments: 20 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

Minor
No `required` list, so every argument is optional.no_required

get_forecast

73 / 100Clear

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

get_cam_timeline

75 / 100Clear

Purpose: 17 / 20
When to use: 10 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

No issues.

get_monthly_climatology

75 / 100Clear

Purpose: 17 / 20
When to use: 10 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

No issues.

get_resort_cams

75 / 100Clear

Purpose: 17 / 20
When to use: 10 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

No issues.

get_season_stats

75 / 100Clear

Purpose: 17 / 20
When to use: 10 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

No issues.

ask

77 / 100Clear

Purpose: 17 / 20
When to use: 5 / 20
Arguments: 23 / 25
Return value: 15 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

No issues.

get_score

78 / 100Clear

Purpose: 17 / 20
When to use: 10 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

get_resort_conditions

80 / 100Clear

Purpose: 17 / 20
When to use: 15 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

No issues.

get_snow_history

80 / 100Clear

Purpose: 17 / 20
When to use: 15 / 20
Arguments: 23 / 25
Return value: 8 / 15
Constraints and side effects: 7 / 10
Examples: 10 / 10

No issues.

get_timelapses

90 / 100Clear

Purpose: 17 / 20
When to use: 15 / 20
Arguments: 23 / 25
Return value: 15 / 15
Constraints and side effects: 10 / 10
Examples: 10 / 10

No issues.

What static scoring cannot tell

This score reads only the text of each description and schema: it says what is written, not what a model will do. Short tools whose names already say what they do, such as browser_close, score low here even when models use them well, and in our measurements current models chose the right tool in one step even from one-line descriptions, as long as the names and schemas differed. What the text cannot show, such as what happens over several steps and whether an added sentence helps or misleads, is what an evaluation measures, on the Pro and Team plans.

Is your server listed here and you would rather it were not? Email support@forecall.dev, and we will take it off within 7 days.

All scored servers