Skip to main content
Glama

check_weather

Retrieves a location’s weather forecast and plan-relevant summary so agents can decide if an outdoor booking is advisable; returns the forecast artifact and payment receipt.

Instructions

Forecast for a location, with the plan-relevant summary an agent needs to decide whether an outdoor booking is a good idea. Costs $0.001 per call, paid in USDC over x402 to x402-weather-guard. Returns the merchant's artifact and the payment receipt.

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

Input Schema

NameRequiredDescriptionDefault
latYesLatitude
lonYesLongitude
dateNoYYYY-MM-DD, defaults to today
railNoPayment rail for this call. Overrides the configured default (auto). auto = whichever rail this agent holds a key for.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden and does well: it discloses the exact call cost, the USDC/x402 payment mechanism, the payment recipient, and that the response includes the merchant artifact and payment receipt. It does not explain failure modes or what the plan-relevant summary contains, but the key economic and payment behavior is covered.

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 the core purpose and then adds cost, payment, and return information. The phrase about the plan-relevant summary is slightly verbose, but every sentence contributes useful context.

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 four fully documented parameters and no output schema, the description covers the essential economic and return-shape details. It could say more about what the artifact contains or how payment failures are handled, but it is sufficient to invoke the tool correctly.

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 the schema already documents lat, lon, date, and rail. The description adds payment context but does not explain parameter formats or the rail override behavior beyond what the schema provides.

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 states a specific resource and outcome: a location forecast plus a plan-relevant summary for deciding whether an outdoor booking is wise. This clearly separates it from commerce siblings such as price_flight or search_hotels.

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 a clear usage context — deciding whether an outdoor booking is a good idea — which implies when an agent should call it. It does not explicitly state when not to use it or name an alternative weather tool, but the context is strong.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.