Skip to main content
Glama

Weather for one lat/lon (paid, x402)

weather_forecast
Read-only

PAID: current conditions plus the next 12 hourly steps for one point, for $0.0100. Coordinates only, no place names; data from MET Norway (api.met.no), attribution rides in the answer. Unpaid, it returns the price; pay with x402 (USDC on Base, Solana, Polygon, Arbitrum, Avalanche, Sei or X Layer) in _meta['x402/payment'] and call again. Feedback: POST /feedback (free). Read daily; no individual reply.

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
latNoLatitude in decimal degrees, -90..90, e.g. 59.9127.
lonNoLongitude in decimal degrees, -180..180, e.g. 10.7461.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/destructive annotations, it discloses cost ($0.0100), the payment protocol and accepted chains, the unpaid fallback that returns a price, the upstream source with attribution handled in the response, and a free out-of-band feedback channel. One mild tension exists: "data from MET Norway (api.met.no)" implies an external fetch while openWorldHint is false, though the result set is bounded and predictable.

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 paid status and price are front-loaded, and most clauses carry real information (source, payment chain list, fallback behavior). The trailing feedback and cadence note ("Read daily; no individual reply") is somewhat tangential but brief enough not to dilute the core.

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 carries the return burden and does so adequately: it states what data comes back (current plus 12 hourly steps), that attribution is embedded, and what an unpaid call returns. Only fine details like units or timestamp format are unspecified.

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 both parameters are already documented with ranges and examples. The description adds useful semantic constraints the schema lacks: coordinates only, no place-name resolution, and a single point per call.

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 names a specific resource and scope: "current conditions plus the next 12 hourly steps for one point," with a stated price. No sibling tool covers weather, and the title plus description make the operation unmistakable without 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?

It gives concrete calling constraints ("Coordinates only, no place names") and an explicit workflow for the paid path: unpaid call returns the price, then pay via x402 in _meta['x402/payment'] and call again. It does not name when to prefer an alternative, but no sibling overlaps this resource, so the practical gap is small.

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