Agent Tools

weather_forecast

Weather forecast for any latitude and longitude: current conditions plus hourly and daily forecast up to 48 hours. Data from MET Norway. Price $0.001 USDC per call via x402. Example output: {"current":{"time":"2026-11-09T15:00:00Z","temperature":12.4,"humidity":72,"wind_speed":18.5,"wind_direction":245,"precipitation_next_hour":0.01,"condition_symbol":"partlycloudy_day"},"hourly":[{"time":"2026-11-09T15:00:00Z","temperature":12.4,"humidity":72,"wind_speed":18.5,"precipitation":0.01,"co

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

Input Schema

Name	Required	Description
`lat`	Yes	Latitude, -90 to 90
`lon`	Yes	Longitude, -180 to 180
`hours`	No	Forecast hours, 1 to 48, default 24
`units`	No	metric (default, temp °C, speed km/h, precip mm) or imperial (temp °F, speed mph, precip in)

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations supplied, the description carries the full burden and does substantial work: it discloses the data provider (MET Norway) and the payment/auth requirement ($0.001 USDC per call via x402), which an agent must know before invoking. Gaps remain around rate limits, error behavior, and attribution obligations, and the embedded output example is truncated mid-field.

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

Conciseness3/5

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

The opening sentence is front-loaded and efficient, but the pasted example JSON is cut off at "precipitation":0.01,"co", making it noisy and partially unusable. A compact schema sketch or a complete, shorter sample would earn the space the truncated blob currently wastes.

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?

Since no output schema exists, the description must convey return shape, and the example does show the current/hourly structure and field names — albeit truncated. Combined with provider and pricing disclosure, an agent has enough to call it correctly; only the incomplete example and absent failure modes keep it below a 5.

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%, with lat/lon ranges, the 1-48 hours bound and default 24, and the metric/imperial enum all documented in the schema. The description only echoes the 48-hour cap and says nothing about units defaults or hours semantics, so it adds no meaning beyond the structured fields. 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?

Names a specific resource (weather forecast), the exact scope (current conditions plus hourly and daily forecast up to 48 hours), and the input domain (any latitude and longitude). No sibling in the catalog covers weather, so there is nothing to confuse it with, and an agent can tell what it returns before opening the schema.

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?

Clear context is given: any coordinate pair, forecast horizon capped at 48 hours, with current conditions always included. There are no exclusions or named alternatives (none exist among siblings), which is the only thing separating this from a 5.

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

All Agent 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?