Skip to main content
Glama

DailyMeteo

Weather values for a location

get_weather
Read-only

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 observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the credit cost model, the DailyMeteo key/account requirement, the 400-row listing cap with per-year summarisation, and automatic CSV saving. These are non-obvious operational traits an agent must know before calling. Remaining gaps are error behaviour and exact return shape.

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?

Two short paragraphs, front-loaded with scope and then the cost/size caveats. Almost every sentence carries information; 'see the server instructions' is a small pointer rather than wasted text.

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 nine-parameter tool with no output schema, the description covers the essential unknowns: pricing, authentication, truncation and CSV fallback, plus a hint that results include per-variable summaries. It stops short of describing the returned data structure or how lat/lon map to a grid cell.

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 the schema already explains lat/lon bounds, date formats, variables and enums. The description reinforces the cost-per-day-and-variable logic that underpins confirm_credits and the 400-row cap behind save_csv, but adds little syntax or constraint detail beyond 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 verb and resource: daily, monthly or annual values for one location and one or more variables from 1961 onward. It is clear enough to separate from siblings like get_climate_normals or find_location, though it never names an alternative explicitly.

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?

It gives decision-relevant context (monthly/annual free, daily costs 1 credit per day and variable, API key or account required), which steers the choice of time_scale. However, there is no explicit when-not guidance or routing to siblings such as get_climate_normals for historical averages.

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.