Skip to main content
Glama

YRUZ Weather Forecast (0.003 USDC)

weather_forecast
Read-onlyIdempotent

Weather for any place on Earth: current conditions (temperature, feels-like, wind, humidity, pressure, cloud, precipitation), the next 48 hours hour by hour and a 7-day forecast with highs, lows and rain, in metric and imperial units, plus active official weather alerts for US locations. Place by name or coordinates. Data: MET Norway (CC BY 4.0) and the US National Weather Service. Price: 0.003 USDC per call, paid with x402 (USDC on Base or Solana, no account, no API key); invalid input is refused before payment and a failed run is never charged. Without a payment the tool returns the x402 PaymentRequired. How to call it: get_example {"tool":"weather_forecast"}. Same tool over HTTP: https://yruz.one/api/weather?q=New+York

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

NameRequiredDescriptionDefault
qNoplace name (required unless lat/lon), e.g. Berlin or Austin, TX
latNolatitude, -90 to 90
lonNolongitude, -180 to 180

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / q / examples
      Added value: +[
      +  "New York"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, open-world), and the description layers on the things annotations can't express: a paywall (0.003 USDC via x402, no account/API key), the pre-payment validation guarantee, the no-charge-on-failure policy, the PaymentRequired response without payment, and upstream data licensing (MET Norway, NWS). That is exactly the kind of behavioral context that matters for a metered external call.

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?

Front-loaded correctly — the payload contents come first and the payment mechanics trail. It's dense but mostly earn-your-place content; the standalone HTTP URL at the end is the weakest sentence, adding length without helping tool selection or invocation from an MCP client.

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?

With no output schema, the description carries the return-value burden and does it: it enumerates the field groups returned (temperature, feels-like, wind, humidity, pressure, cloud, precipitation), the forecast horizons, unit coverage, and alert availability. Combined with the payment and error-behavior notes, an agent has everything needed to call this correctly and interpret what comes back.

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%, so q/lat/lon are already documented with ranges and the unless-lat/lon relationship. The description restates "place by name or coordinates" but adds no new semantics — notably it doesn't clarify unit selection (metric vs imperial) is automatic rather than a parameter, which is the one ambiguity an agent might have.

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?

Opens with a specific verb+resource ("Weather for any place on Earth") and enumerates the exact outputs: current conditions, 48-hour hourly, 7-day with highs/lows/rain, plus US alerts. This is unmistakably distinct from every sibling tool (crypto_price, uptime_check, etc.), so an agent can select it without inspecting 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?

It clearly tells the agent how to supply the location ("Place by name or coordinates") and points to get_example for invocation syntax, which is genuinely useful routing. What's missing is any when-not-to-use guidance or named alternative — there is no statement about coverage limits besides alerts being US-only, and no sibling is referenced as an alternative path.

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.