Running Cat Geo

Weather forecast

weather_forecast

Read-only

The weather forecast at one point: current conditions, hourly values and daily summaries for up to 14 days. Hourly: temperature and feels-like (°C), precipitation (mm), weather code (WMO), wind and gusts (km/h) with direction, cloud and humidity (%), pressure (hPa). Daily: highs and lows, precipitation, strongest wind, sunrise and sunset. Hourly times are UTC; days run from midnight to midnight in the point's own time zone. Use point_report to get the weather together with place, air and rivers, area_report for a grid over a region, route_report for the weather at the time you reach each point of a route. Counts as one request.

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

Input Schema

Name	Required	Description
`lat`	Yes	Latitude
`lon`	Yes	Longitude
`days`	No	Days of forecast, today first

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description adds substantial context beyond that: units for every returned field, UTC hourly times, local-midnight day boundaries, and the note that the call counts as one request. Since there is no output schema, this return-format detail is especially valuable and adequately discloses what the agent will receive.

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?

The description is front-loaded with the core purpose, then supplies return details and alternatives in a compact, information-dense block. Every sentence contributes useful scoping, units, time semantics, or sibling routing guidance.

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?

For a three-parameter weather tool with no output schema, the description fully covers the inputs, return contents, units, time conventions, and alternative tools. It gives an agent enough information to call the tool correctly without opening additional documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so lat, lon, and days are already documented. The description still adds meaningful semantics beyond the schema: the forecast is for a single point, days include daily summaries up to 14, and day boundaries follow the point's local time zone while hourly times are UTC.

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 states a specific verb and resource: "The weather forecast at one point," then enumerates current conditions, hourly values, and daily summaries up to 14 days. It clearly distinguishes this tool from sibling reports by naming point_report, area_report, and route_report with their respective scopes.

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 explicitly routes the agent to alternatives: point_report for weather plus place/air/rivers, area_report for a regional grid, and route_report for weather along a route. The conditions for choosing each alternative are concrete rather than implied.

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

All Running Cat Geo 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?