CoastWise MCP

Find best activity window

find_best_activity_window

Ranks 3-hour windows for a beach day or surf session by scoring consecutive qualifying hours, returning sorted candidates and skipped hours with reasons.

Instructions

Slides a fixed 3-hour block across the requested window at hourly stride and names the most suitable stretch, scoring each block by the mean of its hours with the same rules as rate_activity_conditions. A candidate counts only when all three consecutive hours carry every required Factor; a gap disqualifies rather than bridges, and disqualified hours are reported under skippedHours instead of being ranked. Returns every evaluated candidate sorted by score, the hours that could not be evaluated and why, and best: null with a reason when no 3-hour stretch qualifies.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>",
      "date": "<date>",
      "activity": "<activity>"
    },
    "name": "find_best_activity_window"
  }
}

Input Schema

Name	Required	Description
`date`	Yes	Day to evaluate, in the beach's local calendar. Today through today+6.
`window`	No	Local time window to evaluate, e.g. {"start":"09:00","end":"13:00"}. Omitted → 07:00–19:00.
`activity`	Yes	What the person plans to do.
`latitude`	Yes	Beach latitude in decimal degrees (WGS84).
`longitude`	Yes	Beach longitude in decimal degrees (WGS84).
`skillLevel`	No	Surfer experience. Required when activity is "surfing"; ignored for beach_day.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 1, 2026

TDQS

A4.3/5.0

Behavior5/5

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

With no annotations, the description carries the full burden and does so well: it discloses the strict all-three-hours-required rule, that a gap disqualifies rather than bridges, that unqualified hours are routed to skippedHours instead of being ranked, and that best is null with a reason when nothing qualifies. These are exactly the non-obvious behaviors an agent would otherwise get wrong.

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?

Front-loaded with the core mechanism, and each of the three sentences adds distinct information (algorithm, disqualification rule, return shape). It is dense and jargon-laden ('every required Factor'), but no sentence is filler.

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?

No output schema exists, so the description must describe returns and does: ranked candidates, skipped hours with reasons, and a reasoned null best. It stops short of explaining what a score value means or what constitutes a 'Factor', which leaves some interpretive gaps for a 6-parameter, nested-object tool.

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%, so window defaults, date range, coordinate bounds and the skillLevel/activity dependency are already documented. The description adds only indirect meaning (that 'every required Factor' varies by activity) and no per-parameter syntax or format detail beyond the schema.

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?

States a specific operation (slide a fixed 3-hour block at hourly stride, name the most suitable stretch) with a clearly bounded resource. It also implicitly distinguishes itself from rate_activity_conditions by sharing that sibling's scoring rules while doing block-level selection rather than per-hour rating.

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?

The description makes the selection context clear: use this when you want a ranked set of 3-hour stretches rather than per-hour ratings, since it explicitly says it applies 'the same rules as rate_activity_conditions' but over blocks. However, it never states an explicit when-not or names the sibling as the alternative to pick for hour-level detail.

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

Deploy Server