Skip to main content
Glama

get_weather

Paid $0.01 (x402, USDC Base): current weather for any city worldwide (temperature, feels-like, humidity, wind, conditions) via Open-Meteo with city geocoding.

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": {
      "city": "<city>"
    },
    "name": "get_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityYesCity name, e.g. 'New York'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full behavioral burden and discloses the two things an agent most needs: the call costs $0.01 via x402 in USDC on Base, and city geocoding is handled internally. It omits failure behavior (ambiguous or unknown city names) and any rate or latency expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

A single dense sentence with the cost constraint front-loaded and the resource, provider, and return fields following. Nothing is wasted or repeated.

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 read tool with no output schema, the description covers cost, scope, data source, and returned fields, which is nearly everything needed. The remaining gap is error handling for unresolvable city names.

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?

Schema coverage is 100% and there is only one parameter, so the baseline is met by the schema alone. The description adds meaning beyond it by stating the tool works for 'any city worldwide' with built-in geocoding, telling the agent it need not supply coordinates or a country code.

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 and resource ('current weather for any city worldwide') and enumerates the returned measurements (temperature, feels-like, humidity, wind, conditions), plus the upstream data source. No sibling tool overlaps, so an agent can select it immediately.

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?

'Current weather' implicitly bounds scope (not forecast, not historical), but there is no explicit when-to-use or when-not guidance. Since no sibling covers weather, alternatives are moot, yet the description never says so.

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