Skip to main content
Glama
dailymeteo-mcp

dailymeteo-mcp

by srpp011

Weather values for a location

get_weather
Read-only

Retrieve historical weather and climate normals for any land location from 1961 to today, returning daily, monthly or annual temperature and precipitation values, with CSV export.

Instructions

Daily, monthly or annual values for one location and one or more variables, 1961 to the present.

Monthly and annual values are free. Daily values cost 1 credit per day and variable and need the user's DailyMeteo API key or account (see the server instructions). Results include a summary per variable; series longer than 400 rows are not listed but summarised by year and saved as CSV.

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_weather"
  }
}

Input Schema

NameRequiredDescriptionDefault
endNoLast date, same format
latYesLatitude in decimal degrees (WGS84)
lonYesLongitude in decimal degrees (WGS84)
datesNoIndividual dates instead of a range, same format
startNoFirst date: YYYY-MM-DD (day), YYYY-MM (mon) or YYYY (ann); from 1961
save_csvNoSave the table as CSV (long series are always saved)
variablesNoOne or more of tmean, tmax, tmin (°C), prcp (mm)
time_scaleNoday, mon (monthly) or ann (annual)mon
confirm_creditsNoSet true only after the user agreed to a day request over 1000 credits

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Beyond readOnlyHint and openWorldHint, the description discloses billing rules (1 credit per day and variable for daily), an authentication requirement (DailyMeteo API key), and a concrete truncation behavior (series over 400 rows are summarised by year and saved as CSV). It does not explain the credit-confirmation workflow threshold, but the parameter schema covers that.

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 scope sentence is front-loaded, followed by cost/access notes and then output behavior, which is a sensible ordering. Some of the phrasing is slightly dense and the line-break formatting is awkward, but no sentence is redundant.

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 9-parameter tool with no output schema, the description covers the key gaps: cost, authentication, and how large result sets are returned. What is missing is guidance on obtaining coordinates (a find_location sibling exists) and how this relates to the other historical-data tools.

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 all nine parameters carry their own documentation, making the baseline 3. The description reinforces the credit cost tied to the day time_scale and confirms that results are summarised per variable, but it adds no new syntax or format meaning beyond what the schema states.

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 states a specific resource (daily/monthly/annual weather values for one location and one or more variables) with a clear temporal scope of 1961 to present. It is more precise than the title alone, but it does not name or distinguish itself from plausible siblings such as get_climate_normals or request_point_history.

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 implied through cost and access signals: monthly/annual are free, daily costs credits and requires an API key, which implicitly steers the agent toward cheaper scales when possible. However, there is no explicit when-to-use guidance or named alternative, and the sibling tools are not referenced.

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