Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

weather

[x402 paid: $0.001 USDC on Base] Current weather by city name or coordinates: temperature, wind, conditions (open-meteo, 10-min cache). tools/call returns the live payment challenge.

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

Input Schema

NameRequiredDescriptionDefault
cityNoexample: Moscow

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 meaningful traits: it is paid, the upstream is open-meteo, results are cached for 10 minutes, and tools/call returns a live payment challenge rather than data. What is missing is what the agent should do with that challenge (the x402 retry flow) and whether unpaid calls fail or return a 402 payload.

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 dense sentences with no filler; the payment bracket is front-loaded because it gates invocation. The parenthetical source and cache details are compact. Slight cost is that the payment mechanics sentence is placed after the data description, when it is the more consequential fact.

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 one-parameter tool with no output schema, the description covers source, return fields, cache lifetime, price, and the payment-challenge behavior, which is enough to call correctly. It falls short only on the mechanics of completing payment and on error behavior for unmatched cities.

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 coverage is 100% with a single optional 'city' parameter, so the baseline is 3. The description adds that coordinates may be accepted, but since the schema exposes only 'city', that mention introduces ambiguity rather than clarifying usage.

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?

States a specific verb and resource ("Current weather") and enumerates the returned fields: temperature, wind, conditions. No sibling tool covers weather, so differentiation is by omission rather than by naming. The phrase "or coordinates" is not supported by the schema, which only accepts a city, creating a small scope ambiguity.

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?

The cost line ("$0.001 USDC on Base") gives the agent a real decision input before calling, and the cache note implies repeated calls are cheap. However, there is no when-to-use/when-not guidance, no statement about what happens if the city is unknown, and no named alternative for forecast or historical data.

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