Skip to main content
Glama

SnowSure — Snow & Ski

by ai.snowsure
OverviewDiscussionsAdmin

Resort guide card

get_resort_info
Read-onlyIdempotent

INTERACTIVE RESORT GUIDE CARD (Resort Info sidebar UI) — elevation, vertical, lifts, runs, skiable acres, average snowfall, season dates, ski passes, editorial description, hero/gallery carousel. REQUIRED when the user asks for: resort guide, mountain profile, resort info, lifts/runs/vertical/skiable area, season dates, ski passes, or "tell me about the mountain" (non-weather). Answers single-resort stat questions: base/summit elevation, vertical drop, skiable area, average annual snowfall. Examples: "Aspen Mountain resort guide", "how many lifts at Jackson Hole", "what is the base elevation at Arapahoe Basin". For X-vs-Y stat questions use compare_resorts. Do NOT use get_resort (that shows the snow conditions card).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoResort slug or name, e.g. "portillo" or "Portillo". Required unless `resort` is given.
resortNoSame as `slug`: the resort slug or name. Pass either one.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resortNoStructured resort payload for inline widget rendering.
markdownYesHuman-readable markdown summary (required for ChatGPT Instant mode).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / resort
      Added value: +{
+  "description": "Same as `slug`: the resort slug or name. Pass either one.",
+  "type": "string"
+}
    • changedInput schema / properties / slug / description
      Previous value: -"Resort slug identifier (e.g., \"aspen-mountain\", \"niseko-hanazono-resort\", \"jackson-hole\")"New value: +"Resort slug or name, e.g. \"portillo\" or \"Portillo\". Required unless `resort` is given."
    • removedInput schema / required
      Removed value: -[
-  "slug"
-]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds that it returns an interactive sidebar UI card, which is minor but useful context. No contradictions; the description aligns with annotations and adds a bit of behavioral detail beyond them.

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 description is longer than average but every section earns its place: purpose, required scenarios, examples, exclusions. It is front-loaded with the main purpose and uses bolding for key phrases. Slightly verbose but well-organized.

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, the return format is covered elsewhere. The description covers when to use, what data it provides, alternatives, and exclusions. Nothing needed for correct invocation 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% and both slug and resort are well-documented. The description adds clarity by noting 'Pass either one' and giving an example ('portillo' or 'Portillo'), which is extra semantic value beyond 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?

The description states a specific verb (get) and resource (resort guide card) with a clear list of content (elevation, vertical, lifts, runs, skiable acres, etc.). It explicitly differentiates from siblings: compare_resorts for X-vs-Y and get_resort for snow conditions. The 'REQUIRED when' clause plus examples make the purpose unmistakable.

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?

The description gives explicit when-to-use criteria ('REQUIRED when the user asks for...'), concrete examples, and direct exclusions ('For X-vs-Y stat questions use compare_resorts', 'Do NOT use get_resort'). This fully routes the agent to the correct tool.

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