Skip to main content
Glama

DailyMeteo

List MeteoEurope1km grid archives

list_gridded_files
Read-only

MeteoEurope1km archives on Zenodo (Europe, 1 km, 1961-2020, Cloud-Optimized GeoTIFF), free.

Rasters are Equi7 Europe (EPSG:27704), Int16 in tenths of the unit (°C, mm, hPa), NoData -9999.

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": {
      "variable": "<variable>"
    },
    "name": "list_gridded_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoYears 1961-2020; required for day and mon
periodNoNormal period for ltm_day / ltm_mon_ann; default both
productNoday (one archive per year), mon (one per decade), ann (1961-2020), ltm_day / ltm_mon_ann (normals), ltm_diff (1991-2020 minus 1961-1990)day
variableYestmean, tmax, tmin, prcp or slp (sea-level pressure, daily only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds genuinely useful data context (free access, Equi7 Europe EPSG:27704, Int16 tenths, NoData -9999) that helps an agent consume results. However, it does not disclose what the call actually returns (archive links, file names, paging) or any access constraints, which matters for a read-only discovery tool with no output schema.

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?

Two short sentences, fully front-loaded with the dataset identity, then the technical raster specifications. No filler, and each clause (CRS, dtype, scale factor, NoData) carries operational value.

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?

With four parameters, an enum-driven product selector and no output schema, the description should say what a call yields and how product/years combinations behave. It covers the underlying data thoroughly but leaves the response shape and selection logic to the schema.

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 fully documents years, period, product and variable; baseline 3 applies. The description only echoes the 1961-2020 range and reaffirms the dataset scope, adding no per-parameter meaning 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 resource and its defining characteristics: MeteoEurope1km archives on Zenodo, Europe, 1 km, 1961-2020, Cloud-Optimized GeoTIFF. The verb 'list' comes only from the name/title, so the description never explicitly states that it returns a catalog of downloadable archives, but the resource identity is unambiguous and distinct from the weather/normals siblings.

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 when-to-use guidance, no mention of when to prefer this over get_climate_normals or get_weather for the same variables, and no stated preconditions. A reader must infer from the name alone that this is for bulk gridded archive retrieval rather than point values.

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.