Skip to main content
Glama

Plan my day

plan_my_day
Read-onlyIdempotent

Build modelled suggested runs in time order from forecast weather, sun, snow and mapped terrain. Only plans days inside the reported winter season; summer lift or bike-park operation does not count as open for skiing. Easy, intermediate and advanced exclude expert, freeride and extreme terrain; only expert permits it. Suggestions are not a connected route or live piste status. mode "sun" (Chase the sun): a day's line through lifts and runs that stays in the light, with clock times (clear sky assumed; easy and intermediate keep off black runs).

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

Input Schema

NameRequiredDescriptionDefault
dateNo
modeNo
levelNo
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 / mode
      Added value: +{
      +  "enum": [
      +    "snow",
      +    "sun"
      +  ],
      +  "type": "string"
      +}
  2. 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)"
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely useful behaviour beyond them: results are modelled suggestions rather than live piste status, are ordered in time, and sun mode assumes clear sky. It does not describe result size or what happens when no plan is possible, which keeps it below a 5.

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 purpose is front-loaded in the first sentence and every subsequent sentence carries a real constraint rather than filler. The final sentence, however, is a dense appositive clause that jumps back into mode "sun" semantics after the caveats, so the ordering could be tighter.

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

Completeness3/5

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

For a 4-parameter, read-only planning tool with no output schema the description covers purpose, season gating, and terrain-level semantics well. It still leaves the date parameter and the default/snow mode unaddressed, which an agent needs in order to call it correctly.

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 description coverage is only 25% (resort is the sole documented parameter), so the description has to carry meaning, and it partly does: it defines the level tiers against terrain classes and explains mode "sun". It never explains the "snow" mode or what the date parameter controls and how it interacts with the winter-season constraint.

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?

"Build modelled suggested runs in time order from forecast weather, sun, snow and mapped terrain" names a specific verb (build/plan) and resource (a day's suggested runs), and the negative clauses ("not a connected route or live piste status") separate it from siblings like route_on_mountain. An agent can tell what it will get without opening the schema.

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

Usage Guidelines4/5

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

It gives a real precondition for use: only winter-season days are planned, and summer lift or bike-park operation does not count as open for skiing. It also explains how the level and mode choices steer results, but it never explicitly routes the agent away from look-alike siblings such as sun_on_the_mountain or route_on_mountain.

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