Skip to main content
Glama

Agent Exchange store

Weather by lat/lon, 3-day

kyreos_weather_open_meteo
Read-only

[Kyreos, 0.001 USDC per call via x402 on Base] Current conditions plus a 3-day forecast (temperature, wind, precipitation) for any lat/lon, from Open-Meteo. Input: {"lat":40.71,"lon":-74.0}. HTTP: GET https://store.agentexchange.work/w/weather-open-meteo?q=... Call once without x_payment to get the x402 payment terms (0.001 USDC); call again with x_payment (the signed x402 payment) to get the result.

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

Input Schema

NameRequiredDescriptionDefault
qNo{"lat":40.71,"lon":-74.0}
x_paymentNobase64 x402 payment payload for the terms returned on the first call (0.001 USDC on Base)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond readOnlyHint and openWorldHint, the description discloses the paid x402 requirement, cost, HTTP endpoint, and two-step payment handshake. It does not cover rate limits or error behavior, but it adds substantial economic and authentication context.

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?

The description is front-loaded with purpose and cost, followed by input, endpoint, and payment workflow. It is mostly efficient, though the 0.001 USDC price is stated twice and the paragraph is somewhat dense.

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?

For a paid weather tool with a two-call x402 flow and no output schema, the description supplies endpoint, input example, cost, payment steps, and the forecast fields returned. It could be slightly more complete by clarifying whether q is required despite the schema marking no required parameters.

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 100%, so the schema already documents both q and x_payment. The description repeats the q example and explains the x_payment handshake, but adds little semantic detail beyond what the schema already provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states a specific capability: current conditions plus a 3-day forecast with temperature, wind, and precipitation for any lat/lon, sourced from Open-Meteo. It does not explicitly differentiate from the sibling weather_forecast, so it stops short of a 5.

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 description gives clear operational usage for x402 payment: call once without x_payment to get terms, then call again with x_payment to retrieve the result. However, it does not state when to use this tool versus alternatives such as weather_forecast, leaving selection guidance implicit.

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