Crypto, web, finance and app data tools

US Weather Forecast (NWS)

us_weather_forecast

Official National Weather Service forecast for a US location: 7-day day/night periods or hourly, with temperature, precipitation chance, wind and text forecast. US and territories only.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "us_weather_forecast"
  }
}

Input Schema

Name	Required	Description	Default
`lat`	Yes
`lon`	Yes
`hourly`	No
`periods`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 26, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden; it does state that this is an official read-only NWS feed, which implies low-risk public data. It says nothing about rate limits, latency, or what happens for non-US coordinates, which matters for a geographic-restricted tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence covering provider, output modes, returned fields, and scope, with zero wasted words. Ideal density for a four-parameter lookup tool.

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?

An output schema exists, so return values need no explanation, and the description covers the substantive scope question. The remaining gap is the periods default and coordinate format, minor for a simple lookup but not zero.

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 0%, so the description must compensate, and it only partially does: 'day/night periods or hourly' gives meaning to the hourly and periods parameters but never states the default of 14 or the units/format of lat/lon. An agent would need to open the schema to learn the default period count.

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

Purpose4/5

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

The description names a specific resource and source ('Official National Weather Service forecast') and states the two output modes ('7-day day/night periods or hourly'), so an agent knows exactly what it returns. The 'US and territories only' clause implicitly separates it from the sibling weather_forecast, but that sibling is never named explicitly.

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

Usage Guidelines3/5

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

The geographic restriction ('US and territories only') functions as an implicit when-not condition that routes non-US queries elsewhere, which is more than most definitions offer. However, no alternative is named and there is no guidance on choosing between the periods and hourly modes.

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

All Crypto, web, finance and app data tools 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?