Skip to main content
Glama
Sign In

EM Snow

by uk.co.extreme-media.snow
OverviewDiscussionsAdmin

Get webcams

get_webcams
Read-onlyIdempotent

Get nearby webcam images and their source links, with the required provider credit.

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_webcams"
  }
}

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.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: results include source links and carry a mandatory provider-credit attribution requirement, which constrains how an agent may present the output. It does not say how many webcams come back or whether imagery is live versus cached.

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?

A single tight sentence with zero filler, front-loading the resource and then the return payload and its attribution obligation. Every clause carries information an agent needs.

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?

For a one-parameter read tool with full schema coverage and a rich annotation set, the description covers purpose, return content and the attribution constraint. The only meaningful gap is the absence of any routing hint against overlapping media/imagery siblings.

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?

Schema coverage is 100% and the single 'resort' parameter is fully documented in the schema, including the name-or-numeric-id forms and the pointer to search_resorts. The description adds nothing about the parameter beyond the word 'nearby', so the baseline 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 names a specific verb and resource ('Get nearby webcam images') and also states what comes back (source links plus provider credit), so an agent knows exactly what the tool returns. It stops short of differentiating itself from plausible siblings like get_resort_media or get_resort_media-style tools, so it is clear but not sibling-distinguishing.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no named alternative for obtaining media or imagery. The word 'nearby' hints that results are proximity-based around the resort, but an agent must infer that from the phrasing rather than being told.

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

All EM Snow 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