Skip to main content
Glama

DailyMeteo

Climate normals 1961-1990 vs 1991-2020

get_climate_normals
Read-only

Climate normals for 1961-1990 and 1991-2020 and the change (newer minus older). Free.

Without `month`, time_scale=mon returns all 12 months. Annual precipitation normals are yearly totals.

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": {
      "lat": "<lat>",
      "lon": "<lon>"
    },
    "name": "get_climate_normals"
  }
}

Input Schema

NameRequiredDescriptionDefault
dayNoDay of month, required for time_scale=day
latYesLatitude in decimal degrees (WGS84)
lonYesLongitude in decimal degrees (WGS84)
monthNoOnly this month (mon), or the month of the day (day)
variablesNoOne or more of tmean, tmax, tmin (°C), prcp (mm)
time_scaleNoann (year), mon (by month) or day (one calendar day)mon

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare this is a read-only, open-world lookup, so the safety profile is covered. The description contributes the cost signal ('Free') and the expansion behavior that omitting `month` at time_scale=mon returns all 12 months, but says nothing about response shape, coverage area or failure behavior for out-of-range coordinates.

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?

The opening sentence front-loads the two normals periods and the change, and the supporting notes are short one-liners. The fragment style with trailing whitespace is a minor blemish rather than bloat.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter read-only tool with no output schema, the definition explains what the data represents and two important default behaviors, but it never sketches the returned structure (how the older/newer/change values are keyed) nor how it relates to get_weather. Adequate to call correctly, thin for interpreting 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 all six parameters are already documented, which sets the baseline at 3. The description adds genuine semantics beyond the schema for `month` (omitting it returns all 12 months) and for prcp under ann (yearly totals), but the `day` parameter and its 'required for time_scale=day' behavior are left entirely to the schema.

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 (climate normals for 1961-1990 and 1991-2020) plus the derived change value, so an agent knows exactly what data this returns. It falls short of 5 because it never contrasts itself with the sibling get_weather, which an agent could easily confuse with a normals lookup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance: nothing says to prefer this over get_weather for historical baselines, and no prerequisites or limits are stated. 'Free' is a cost note rather than a selection criterion, leaving usage only loosely implied by the word 'normals'.

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.