Skip to main content
Glama

zato: Ethereum & Base Data API (pay-per-call x402)

Current weather and 24 h forecast

weather
Read-only

Current weather and forecast for any place: temperature, feels-like (wind chill), wind speed and direction, humidity, pressure, cloud cover, precipitation and conditions now, plus an hourly 24-hour forecast. Input: {lat, lon} or {city}. Data: MET Norway (CC BY 4.0), geocoding © OpenStreetMap contributors (ODbL). Price: $0.001 USDC per call (x402 v2, Base). Free demo: https://api.zato.org/demo/weather

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

Input Schema

NameRequiredDescriptionDefault
latNo
lonNo
cityNoPlace name, e.g. "Berlin" or "Paris, France" (used when lat/lon are not given)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations declare read-only and open-world, but say nothing about cost or provenance; the description adds that each call costs $0.001 USDC via x402 v2 on Base, names the upstream data sources and their licenses, and points to a free demo. That paid-call requirement is critical context an agent cannot get from the annotations. It stops short of rate limits or failure behavior, so not a 5.

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 capability and returned fields are front-loaded, followed by the input contract, then provenance and pricing. Every clause carries information; the license and pricing lines are required disclosure for this paid, attributed data source.

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?

With no output schema, the description correctly does the work of listing returned quantities, and it covers cost, source, and demo access for a paid external call. It omits unit conventions (metric vs imperial) and the forecast's reference timezone, which an agent would want before presenting values to a user.

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 only 33% – just the city parameter is documented, and lat/lon carry only numeric bounds. The description adds the either/or input contract, but the precedence rule ("used when lat/lon are not given") already lives in the city field's schema description, so this largely restates structured data rather than compensating for the gap.

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 opens with a specific verb+resource ("Current weather and forecast for any place") and then enumerates the exact data returned, including the 24-hour hourly forecast. Nothing in the sibling list covers weather, and the scope (current + 24h, any place) is unambiguous.

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?

It states two input modes, {lat, lon} or {city}, which implies when each form applies, and no alternatives exist among the siblings. However there is no explicit when-to-use/when-not guidance, no note on which input wins if both are supplied, and no mention of error cases such as an unresolvable city name.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources