Crypto, web, finance and app data tools

Weather Forecast

weather_forecast

Current weather and a daily forecast (up to 9 days) for any city, address or coordinates: temperature, min/max, humidity, wind, clouds, pressure, sky and precipitation, from the Norwegian Meteorological Institute. Use for travel, events, logistics or energy planning.

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

Input Schema

Name	Required	Description	Default
`lat`	No
`lon`	No
`days`	No
`place`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations, the description carries the full burden; it usefully discloses the upstream data source (Norwegian Meteorological Institute) and the 9-day forecast ceiling. It omits rate limits, geographic coverage limits, and — most importantly for a mutation-free but multi-input tool — what happens when both `place` and `lat`/`lon` are supplied, or when neither is.

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?

Two sentences, front-loaded with the capability and horizon before the variable list and use cases. The variable enumeration ('temperature, min/max, humidity, wind, clouds, pressure, sky and precipitation') is slightly long but earns its place by telling the agent what data it will receive.

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?

An output schema exists, so return-value explanation is not required, and the forecast horizon and source are covered. The gap is on the input side: with four optional, undocumented parameters, an agent still cannot tell how to compose a valid call from the description alone.

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 0%, so the description must compensate; it maps 'city, address or coordinates' onto `place` vs `lat`/`lon` and 'up to 9 days' onto `days`. It never states that `lat` and `lon` must be paired, that inputs are optional, or the precedence between `place` and coordinates, leaving the most error-prone aspect undocumented.

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+resource (current weather and a daily forecast, up to 9 days) along with the accepted location forms (city, address, or coordinates) and the exact variable set returned. No sibling overlaps with this capability, so an agent can identify it immediately.

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 closing clause 'Use for travel, events, logistics or energy planning' gives usage contexts, but there is no guidance on when NOT to use it, no mention of historical weather or alternatives, and no note on which location input to prefer when the caller has both.

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?