Skip to main content
Glama

weather

Current weather + hourly 24h forecast for lat/lon. $0.01 USDC on Base (x402).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
latYes
lonYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key behavioral fact that a call costs $0.01 USDC on Base via x402 — important, non-obvious context an agent needs before invoking. It does not, however, explain the payment mechanics (wallet requirement, how the x402 challenge is satisfied), error behavior for unfunded callers, or rate limits, which are the practical risks of this tool.

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?

Two tight sentences, with the payload (current weather + 24h hourly forecast) front-loaded and the cost disclosure second. Nothing is wasteful, though the second sentence could be slightly more explicit that payment is a precondition rather than a footnote.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no output schema and no annotations, the description does not say what the response looks like (fields, units, timezone of the hourly series) and leaves the payment requirement underspecified. It gives enough for a rough call but not enough to handle the paid flow or parse results confidently.

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?

Zero schema description coverage means the description must define both parameters, and it names the lat/lon concept so the agent knows what the two numeric fields mean — a genuine contribution beyond the bare {"type":"number"} schema. It still omits units, valid ranges (e.g. -90..90), and accepted precision, so it does not fully compensate for the 0% coverage.

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 concrete resource and scope: current conditions plus an hourly 24-hour forecast keyed to lat/lon. That is unambiguous and clearly distinct from every listed sibling (eth_price, fetch_page, wallet_balances, wiki_summary), 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 Guidelines3/5

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

Usage is only implied by the resource name and the lat/lon requirement; there is no explicit when-to-use statement, no mention of what to do instead when coordinates are unavailable, and no note that this competes with the other paid tools in the catalog. The mention of x402 hints at a required payment flow but does not tell the agent when that flow is worth invoking.

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