Skip to main content
Glama

Weather That Doesn't Suck

by com.weatherthatdoesntsuck
OverviewDiscussionsAdmin

When is the best time?

find_best_weather_window
Read-onlyIdempotent

Finds the best time on a day for an activity. Returns the best window, an alternate, and any clearly bad stretch, each with a short reason. Windows are stretches, not exact hours: when several start times are about equally good they are reported as one stretch, and when the whole day is about the same it says so. Use it for "when should I go?", "what's the best time Saturday?", "Kilian and I want to hike Saturday". Give a date such as "Saturday", "tomorrow" or 2026-10-03. If nothing on the day is good it says so and names the least bad stretch.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoThe day to search. Defaults to today. A part of a day ("tomorrow morning") narrows the search to it, and "this weekend" compares both days. An ISO 8601 time such as 2026-10-03T18:00:00-05:00 (read in the place's own time zone when it has no offset), or plain words: "now", "tonight", "tomorrow morning", "Saturday", "6 PM", "between 6 PM and midnight". A bare hour with no AM or PM is refused rather than guessed.
unitsNoimperial (F, mph, inches) or metric (C, km/h, mm). Defaults to imperial in the United States and metric elsewhere.
activityYesWhat the person is doing. One of: walking, hiking, trail_running, road_running, cycling, camping, hunting, fishing, yard_work, construction, painting_finishing, general_outdoor. Plain words work too ("run", "hike", "stain the deck"). "Running" with no more words is treated as road_running.
latitudeNoLatitude in degrees. Use with longitude instead of location.
locationNoA place name such as "Glenbeulah, WI" or "Greenbush, Wisconsin", or coordinates as "43.79,-88.05". Add the state or country for small towns, because a bare "Greenbush" matches several places.
intensityNoHow hard the effort is, which changes what to wear. Defaults to the usual effort for the activity.
longitudeNoLongitude in degrees, west negative. Use with latitude instead of location.
duration_hoursNoHow long the activity lasts. Defaults to the usual length for the activity, and says so.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations cover the safety profile (readOnly, idempotent, non-destructive), and the description goes well beyond them: it explains that windows are stretches rather than exact hours, that equally-good start times are collapsed, that a uniform day is reported as such, and that a bad day yields a least-bad stretch with a reason. This is exactly the behavioral context an agent needs to interpret the result.

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?

Purpose and output shape are front-loaded, then usage examples, then the date input hint. It is a bit long and repeats the 'says so when the day is uniform / nothing is good' idea, but every sentence still carries usable information.

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

Completeness5/5

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

There is no output schema, so the description must explain the return shape, and it does: best window, alternate, bad stretch, each with a short reason, plus fallback behavior on poor days. With 8 parameters all schema-documented and annotations covering safety, nothing an agent needs to call and interpret this tool is missing.

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 100%, so every parameter is already documented, including date syntax, units, and activity enums. The description largely restates the date guidance ('Give a date such as Saturday, tomorrow or 2026-10-03') rather than adding new meaning, so the baseline 3 applies.

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 verb and resource ('Finds the best time on a day for an activity') and immediately enumerates what it returns (best window, alternate, bad stretch). This clearly separates it from forecast/weather siblings like get_forecast or outdoor_activity_weather, which report conditions rather than a recommended time window.

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?

Gives concrete trigger phrases ('when should I go?', 'what's the best time Saturday?') and the acceptable date forms, which tells the agent exactly when this tool is the right pick. It stops short of naming an alternative sibling or stating when not to use it, so it does not reach a 5.

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

All Weather That Doesn't Suck 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