Skip to main content
Glama

Weather now (5 sats L402 or $0.005 USDC x402)

get_weather_now
Read-only

Temperature (F), wind and a text summary for a US city/ZIP or lat/lon, about 1 km resolution, cached up to 15 minutes (5 sats) — use this for a rough current check; weather_current adds humidity, Celsius and the station. Price: 5 sats (Lightning) or $0.005 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"weather_now","data":{"coverage":"us","source":"noaa_nws","place":{"city":"Austin","state":"TX","lat":30.27,"lon":-97.74},"conditions":{"as_of":"2026-11-15T20:00:00Z","text":"Cloudy","temperature_f":53.6,"wind_speed_mph":8.0}},"metadata":{"cost_sats":5}} Pay: Call it, get HTTP 402 (or MCP payment_required) with a Lightning invoice and macaroon, pay the invoice, then retry with Authorization: L402 <macaroon>:<preimage>. Or pay in USDC on Base via x402: sign the 402's x402 requirement (PAYMENT-REQUIRED header, or accepts in the JSON body) and retry with the PAYMENT-SIGNATURE (x402 v2) or X-PAYMENT (v1) header; only a 200 is settled.

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

Input Schema

NameRequiredDescriptionDefault
qNoSame as location: US city or ZIP.
latNoLatitude (−90 to 90). Use with lon.
lonNoLongitude (−180 to 180). Use with lat.
zipNo5-digit US ZIP code.
stateNoUS state or territory code (alerts only), e.g. TX.
locationNoUS city ('Austin, TX') or 5-digit ZIP. Alias: q.
x402_paymentNoOptional x402 payment (USDC on Base): base64 PaymentPayload (v2, or v1 X-PAYMENT format) signed for accepts[0] of this tool's payment_required result. Alternative to params._meta['x402/payment']. Omit both to receive the payment requirements.
l402_credentialNoOptional L402 credential '<macaroon>:<preimage_hex>' (or 'L402 <macaroon>:<preimage>') from a paid invoice or an active subscription. Omit it to receive the Lightning invoice and macaroon.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, and the description adds substantial context beyond them: the NOAA/NWS source, 15-minute caching, the full L402 and x402 payment handshake, and the rule that only a 200 counts as settled. It stops short of detailing failure/timeout behavior or coverage limits beyond 'us', which keeps it below 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.

Conciseness4/5

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

The core purpose, resolution, and cache constraint are front-loaded before the payment material, and the sample response is clearly labelled illustrative. The payment paragraph is dense and long, but each part carries operational information an agent needs to complete a paid call.

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 supplies a concrete response sample covering fields, coverage, source, and cost, and it explains the full 402 payment retry flow for both L402 and x402. Given the tool is an untrusted, zero-required-param paid lookup, an agent has everything needed to call and complete it.

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 every parameter is already documented, including the aliases (q vs location) and the payment header parameters. The description only echoes the location forms and the payment mechanics, adding no syntax or format detail the schema lacks. 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?

States a specific verb (current check) plus the exact resources returned (temperature in F, wind, text summary), the accepted location inputs (US city/ZIP or lat/lon), the ~1 km resolution and the 15-minute cache. It also explicitly distinguishes itself from the sibling get_weather_current by naming what that tool adds (humidity, Celsius, station).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives direct when-to-use guidance ('use this for a rough current check') and names the alternative (weather_current) along with the condition that selects it (need for humidity/Celsius/station). Nothing about routing is left to inference.

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