Skip to main content
Glama

Weather current (10 sats L402 or $0.01 USDC x402)

get_weather_current
Read-only

Current conditions for lat/lon or a US city/ZIP (NOAA NWS in the US; MET Norway elsewhere) — use this for a point weather check. Price: 10 sats (Lightning) or $0.01 USDC on Base (x402). Sample (illustrative, not live): {"status":"success","endpoint":"weather_current","data":{"coverage":"us","source":"noaa_nws","place":{"lat":30.27,"lon":-97.74,"city":"Austin","state":"TX","zip":null},"conditions":{"as_of":"2026-11-15T20:00:00Z","text":"Cloudy","temperature_c":12.0,"temperature_f":53.6,"relative_humidity_percent":70,"wind_speed_mph":8.0}},"metadata":{"cost_sats":10}} 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_current"
  }
}

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. Changed1 schema field changed
    • addedInput schema / properties / x402_payment
      Added value: +{
      +  "description": "Optional 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.",
      +  "type": "string"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds the decisive behavioral facts — cost (10 sats / $0.01 USDC), the 402 payment handshake, L402 macaroon/preimage retry, x402 header variants, and the fact that only a 200 means settled. It also shows the response envelope and the data source selected by region, which annotations cannot convey.

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?

Purpose and pricing are front-loaded, and the payment instructions are necessary rather than filler. The illustrative sample JSON is bulky and the price is restated from the title, so a slight trim is possible, but nothing is genuinely off-topic.

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 an 8-parameter paid tool with no output schema, the description covers cost, payment mechanics, sources, and a sample response — most of what an agent needs. The notable gap is that all parameters are optional, yet the description never states that at least one of location/q or lat+lon must be supplied.

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 alias relationships and payment credential formats. The description only restates the location modes at a high level and adds no constraint the schema lacks, which is the expected baseline-3 case.

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 names a specific verb and resource ('Current conditions') and states the two input modes (lat/lon or US city/ZIP) plus the upstream sources (NOAA NWS in the US, MET Norway elsewhere). It is clearly distinguishable from a forecast or alerts tool, though it never names those siblings explicitly.

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?

'Use this for a point weather check' gives clear positive guidance, and the geographic coverage note tells the agent when the tool will work (US vs elsewhere). It stops short of explicit exclusions, e.g. pointing to get_weather_forecast for multi-day outlooks or get_weather_alerts for warnings.

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