Skip to main content
Glama

Weather for a place or a coordinate: current conditions

weather
Read-only

Weather for a place or a coordinate: current conditions, the next 48 hours and 7 days (temperature, precipitation, wind, symbol). Forecast from MET Norway, cached until its own expiry time. Attribution: Data from MET Norway (CC BY 4.0). Related tools on this server, for a different need: weather_alerts when you need to check active US weather alerts for a state or point. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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
latNoLatitude, -90 to 90
lonNoLongitude, -180 to 180
placeNoOr a place name, geocoded first

Output Schema

NameRequiredDescriptionDefault
dailyNo
unitsNo
hourlyNo
sourceNo
currentNo
locationNo
checkedAtNo
attributionNo
forecastUpdatedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is known. The description adds genuinely useful context beyond them: the upstream source (MET Norway), cache-until-expiry behavior, CC BY 4.0 attribution obligations, and a per-call price with the note that failed calls are not charged. That earns credit, though it stops short of describing response shape or staleness guarantees.

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?

Front-loaded with purpose, then progressively narrowing to source, cost, and the sibling alternative, which is the right order. It is a single dense paragraph covering many topics; nothing is clearly wasted, but the pricing clause is long enough to slightly dilute the core signal.

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?

An output schema exists, so return-value detail is not required, and the definition covers source, caching, attribution, cost, and alternatives. The remaining gap is minor: no statement about how lat/lon versus place resolve when both are passed, or about freshness of cached results.

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%, so lat/lon ranges and the 'geocoded first' note for place are already documented in the schema. The description restates the place-or-coordinate duality but adds no precedence rule for when both are supplied, so the baseline 3 applies.

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 ('Weather for a place or a coordinate') plus the exact scope: current conditions, next 48 hours, and 7 days, with the returned fields named (temperature, precipitation, wind, symbol). It explicitly separates itself from weather_alerts, so an agent can pick between them without opening a schema.

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?

Gives an explicit alternative and the condition that selects it ('weather_alerts when you need to check active US weather alerts for a state or point'), which is strong routing guidance. It does not state a when-not condition for this tool itself (e.g., that it does not cover severe-weather alerts outside the US), so it falls just short of the top mark.

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