Skip to main content
Glama

Weather

weather
Read-only

Get current weather and 7-day forecast for any location by latitude/longitude. Returns temperature, humidity, wind, precipitation, and conditions. Costs $0.001 USDC per call.

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": {
      "latitude": "<latitude>",
      "longitude": "<longitude>"
    },
    "name": "weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
latitudeYesLatitude of the location
locationNoHuman-readable location name (e.g. 'New York')
longitudeYesLongitude of the location

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?

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new operational context in 'Costs $0.001 USDC per call,' which tells the agent this is a paid, metered call. It also enumerates the returned measures, which compensates for the missing output schema. Minor gap: it doesn't say whether cost is per call regardless of failure or whether payment/auth setup is needed.

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?

Three short sentences, each carrying distinct information: capability, return values, cost. The capability is front-loaded and nothing is redundant with the title.

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?

With no output schema, the description correctly enumerates return fields, and it discloses the paid nature of the call — enough for an agent to call it and interpret the result. The remaining hole is the optional 'location' parameter's relationship to lat/long, which is left to the caller to infer.

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 all three parameters; the description only reinforces that lat/long are the addressing mechanism. It never clarifies the role of the optional 'location' string (alternative to coordinates? display label?) or what happens if both forms are supplied, which is the one ambiguity the schema leaves open.

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 ('Get current weather and 7-day forecast') plus the input domain ('by latitude/longitude'). No sibling tool in the list covers weather, so differentiation is trivially achieved, but the scope is still stated precisely enough that an agent knows exactly what it gets.

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?

'for any location by latitude/longitude' gives clear applicability context, and there are no competing weather siblings to route away from. It stops short of explicit when-not guidance (e.g. whether historical weather or alerts are out of scope), which keeps it below a 5.

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