Weather That Doesn't Suck

Weather now and the days ahead

get_weather

Read-onlyIdempotent

Plain-language weather for a place: one sentence first, then current conditions, the next 24 hours, the next 7 days, and official alerts. Use it for "what's the weather", "do I need a jacket", "is it going to rain". For a decision about doing something outdoors (a run, a hike, staining a deck), use outdoor_activity_weather instead: it answers "should I?", not just "what is it?". data.current says whether it is a station observation, a model estimate, or a forecast hour. data.alerts.status says whether "no alerts" can be believed: only "ok" means we checked. Answers carry their sources, how old the data is, and say so when it came from cache.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_weather"
  }
}

Input Schema

Name	Required	Description
`hours`	No	Hours of hourly detail to include. Default 24.
`units`	No	imperial (F, mph, inches) or metric (C, km/h, mm). Defaults to imperial in the United States and metric elsewhere.
`latitude`	No	Latitude in degrees. Use with longitude instead of location.
`location`	No	A 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.
`longitude`	No	Longitude in degrees, west negative. Use with latitude instead of location.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 4, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the description is free to add the harder context and does: `data.current` distinguishes station observation, model estimate, and forecast hour, `data.alerts.status` distinguishes a verified "no alerts" from an unchecked one, and results carry sources, data age, and cache status. These are trust-critical traits no annotation conveys.

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 purpose and scoped tightly, with no filler paragraphs. It runs long across several clauses and quote-heavy examples, but each sentence carries distinct routing or behavioral 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?

With no output schema, the description compensates by explaining the meaning of key response fields (`data.current`, `data.alerts.status`) and the provenance/age/cache behavior of answers. An agent knows what to expect back and how much to trust it.

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 the schema already documents hours, units, location, latitude, and longitude. The description adds no parameter-level detail beyond that, which matches the baseline 3 when structured fields do the heavy lifting.

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?

The description gives a specific verb+resource (plain-language weather for a place) and enumerates exactly what the answer contains: one sentence, current conditions, 24 hours, 7 days, alerts. It also distinguishes itself from the nearest sibling by naming outdoor_activity_weather and contrasting "what is it?" with "should I?".

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

Usage Guidelines5/5

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

It supplies trigger phrases ("what's the weather", "do I need a jacket", "is it going to rain") and an explicit exclusion with a named alternative for outdoor-decision queries. This is exactly the when/when-not/alternative structure the rubric rewards.

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 tools Inspect

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

Need Help?