Skip to main content
Glama

weather

Read-only

Retrieve current conditions and 1–16 day forecasts for a place or coordinates, with metric or imperial units.

Instructions

Current weather and 1-16 day forecast for a place or "lat,lon" (Open-Meteo).

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

Input Schema

NameRequiredDescriptionDefault
daysNo
placeYes
unitsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.2

TDQS

A3.7/5.0
Behavior3/5

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

With readOnlyHint=true already declaring a safe read, the description adds the useful data source (Open-Meteo) and the forecast horizon. It does not disclose defaults for days or units, whether missing locations error out, or any rate/coverage limits from the upstream provider, so the added context is moderate rather than rich.

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 front-loaded sentence that packs scope, forecast range, input format, and data source with no filler or repetition.

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 three-parameter read-only tool with no output schema, the description covers what it returns at a high level and how to address a location. It stops short of stating defaults or limits for days/units and says nothing about response shape, which keeps it just under fully complete.

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 description coverage is 0%, so the description must carry parameter meaning and it largely does: 'place' is documented as either a place name or a "lat,lon" pair, and 'days' is bounded to 1-16 via the forecast-range wording. Only 'units' is left to the schema's self-explanatory metric/imperial enum, which is a minor gap.

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?

The description names a specific resource (weather) with two concrete scopes: current conditions and a 1-16 day forecast, plus the accepted location input format (place name or "lat,lon"). It is unambiguous against a sibling set that contains no other weather tool, though it does not explicitly say what it is not for.

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?

Usage is only implied: an agent can infer this is the tool for any weather query, but there is no statement of when to prefer it, no prerequisite, and no exclusion (e.g. historical weather or hourly breakdowns are not addressed). The location-format hint is the only actionable guidance offered.

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