Skip to main content
Glama

Get resort media

get_resort_media
Read-onlyIdempotent

Get images for a resort that vision-capable assistants can show: nearby webcams with provider credit, a Wikimedia Commons photo with its per-file licence, author and source page, the EM Snow sun and shade teaser where one exists, and the resort page link. No trail-map image is available.

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": {
      "resort": "<resort>"
    },
    "name": "get_resort_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
resortYesResort name such as 'Zermatt', or numeric resort id such as 675 (from search_resorts)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / resort / description
      Added value: +"Resort name such as 'Zermatt', or numeric resort id such as 675 (from search_resorts)"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive and closed-world behavior, so the description's job is to add context — which it does: it discloses attribution/licence obligations (provider credit, per-file licence, author, source page), notes that the sun-and-shade teaser exists only 'where one exists', and explicitly rules out a trail-map image. Since there is no output schema, spelling out the returned components carries real weight.

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?

It opens with the core purpose and then lists payload components in one dense sentence, closed by a short negative constraint ('No trail-map image is available'). Every clause carries information, though the enumeration is long enough that a bulleted or more segmented phrasing would scan faster.

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 no output schema, the description must convey the return shape, and it does so component by component, including attribution fields and the possibility of missing items. Remaining gaps (image format/size, pagination, what happens for a resort with no imagery) are minor for a read-only lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter with 100% schema description coverage, and the schema already explains that it accepts a resort name like 'Zermatt' or a numeric id from search_resorts. The description adds no further meaning about the parameter, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Get images for a resort') and then enumerates exactly what comes back: webcams with provider credit, a Wikimedia Commons photo with licence/author/source, the sun-and-shade teaser, and the resort page link. It is clearly a media-bundle tool rather than a conditions or webcam-list tool, though it does not explicitly distinguish itself from the sibling get_webcams.

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 phrase 'that vision-capable assistants can show', which signals the tool is for clients able to render images. Beyond that there is no when-to-use/when-not guidance and no named alternative (e.g. get_webcams) for agents that only need webcam URLs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources