Skip to main content
Glama

Sun on the mountain

sun_on_the_mountain
Read-onlyIdempotent

Show modelled sun and shade windows for eight slope aspects, with local terrain-horizon shading where DEM coverage exists.

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": "sun_on_the_mountain"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNo
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

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description nevertheless adds real value beyond them: 'modelled' signals simulated rather than observed data, and 'where DEM coverage exists' warns of partial/uneven coverage. It says nothing about what the output looks like (times? per-aspect table?) or how it is ordered.

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 is a single front-loaded sentence with no filler, and the coverage caveat sits correctly at the end as a qualifier. The terseness is close to the point of ambiguity, but every word carries information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a computation tool with no output schema, so the description carries the burden of explaining what a 'window' is and how eight aspects are presented — and it does not. Combined with the silent 'date' parameter and absent usage guidance, an agent would have to guess both the return shape and the invocation context.

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

Parameters2/5

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

At 50% schema coverage, the description must compensate, and it does not: the 'resort' parameter is already well documented in the schema (name or numeric id from search_resorts), but 'date' is undocumented in both schema and description. The description never mentions the date parameter, its format, or its default behavior (e.g., today when omitted).

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

Purpose3/5

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

The description names a specific verb ('Show') and resource ('modelled sun and shade windows'), plus a granularity ('eight slope aspects'), so the general subject is clear. However, 'sun and shade windows' is unexplained jargon — it does not say these are time intervals — and nothing distinguishes this from close siblings like best_time_to_go or get_conditions.

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 guidance, no prerequisite or exclusion, and no named alternative for obtaining sun information another way. The agent must infer the use case entirely from the tool name and the phrase 'modelled sun and shade windows'.

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