Skip to main content
Glama

SnowSure — Snow & Ski

by ai.snowsure
OverviewDiscussionsAdmin

Flights to the powder

find_flights_to_powder
Read-onlyIdempotent

Complete the trip: from a resort, find the nearest gateway airport(s) and get flight-search links from your home airport. The "get there" leg of the funnel — pair with find_best_powder / find_powder_trips (find fresh snow) → this → book_lodging (stay). Args: resort (slug, required — use search_resorts to resolve a name), optional origin (your home-airport IATA like DEN, or a city name).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugNoResort slug or name, e.g. "portillo" or "Portillo". Required unless `resort` is given.
originNoYour departure airport IATA (e.g. DEN, LHR) or a city name. Optional — omit for an origin-less flight search.
resortNoSame as `slug`: the resort slug or name. Pass either one.

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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / resort / description
      Previous value: -"Resort slug (use search_resorts first if you only have a name)."New value: +"Same as `slug`: the resort slug or name. Pass either one."
    • addedInput schema / properties / slug
      Added value: +{
+  "description": "Resort slug or name, e.g. \"portillo\" or \"Portillo\". Required unless `resort` is given.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "resort"
-]
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: the tool returns 'flight-search links' rather than bookings, and it selects 'nearest gateway airport(s)', which explains the underlying logic. It does not describe edge cases like no flights found, but given the strong annotation coverage this is acceptable.

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 dense but efficient: it front-loads the core purpose, then gives funnel context, then summarizes args in a compact line. The funnel metaphor is useful but slightly verbose; still, every sentence contributes either purpose, usage, or parameter guidance. It is appropriately sized for a tool with three parameters.

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 and annotations covering the read-only/idempotent behavior, the description only needs to carry usage and selection context, which it does well. The main gap is the unresolved ambiguity between the slug and resort parameters, which could confuse an agent about which to pass. Overall, the agent can select and invoke the tool correctly with the information provided.

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 description coverage is 100%, so the baseline is 3. The description adds value by marking the resort argument as required (clarifying logical necessity despite the schema showing no required fields) and by advising use of search_resorts to resolve names. However, it does not explicitly explain the relationship between the duplicate slug and resort parameters, which introduces minor ambiguity.

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 and resource: 'find the nearest gateway airport(s) and get flight-search links from your home airport.' It differentiates itself from siblings by explicitly labeling itself the 'get there' leg of the funnel and naming find_best_powder/find_powder_trips and book_lodging as the surrounding steps. This leaves no doubt about what the tool does.

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 funnel chain 'find fresh snow → this → book_lodging' explicitly positions the tool in the trip workflow and names its natural alternatives. It also instructs the agent to use search_resorts to resolve a resort name, providing concrete pre-processing guidance. This is clear when-to-use and when-to-use-other-tools information.

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