Skip to main content
Glama

fetch_era5_pressure_levels

Download ERA5 monthly mean atmospheric data for a specified pressure level and month, with optional geospatial filtering and multi-year support.

Instructions

Downloads ERA5 monthly mean data on specific pressure levels for a given month across one or more years.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eastNoEastern longitude (e.g., 20 for 20E) Example: fetch_era5_pressure_levels('temperature', 500, '2023', '01', 'temp_500hpa.nc', north=44, west=-10, south=36, east=4)
westNoWestern longitude (e.g., -10 for 10W)
yearYesThe year(s) for the data (e.g., '2023' or ['2021', '2022', '2023']).
monthYesThe month for the data (e.g., '01', '12').
northNoNorthern latitude (e.g., 60 for 60N)
southNoSouthern latitude (e.g., 30 for 30N)
variableYesThe variable to download (e.g., 'geopotential', 'temperature').
pressure_levelYesThe pressure level in hPa (e.g., 500, 850, 1000).
output_filenameYesThe local filename for the downloaded data (e.g., 'data/raw/geopotential_500hpa.nc').

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the burden. It clearly identifies the operation as a download (non-destructive retrieval), which is helpful. However, it does not disclose potential behavioral traits such as overwrite behavior, download size/time, authentication needs, or return format beyond what the output schema implies.

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, well-structured sentence that is front-loaded with the core action and resource. No redundant or filler content.

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?

Given the tool complexity (9 params) and presence of an output schema, the description provides the essential distinction (monthly mean, pressure levels) and the temporal scope. It could mention the alternative hourly/single-level options, but the description is adequate for a straightforward download tool.

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 baseline is 3. The description adds minimal semantics beyond the schema, only reinforcing that the data is monthly mean and spans years. No new parameter-level meaning is introduced.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Downloads') and identifies the exact resource (ERA5 monthly mean data) with key qualifiers (specific pressure levels, given month, one or more years). It clearly distinguishes from sibling tools that fetch hourly data or single levels.

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?

The description implies use for monthly mean pressure-level data but does not explicitly state when to choose this over alternatives like fetch_era5_hourly_pressure_levels or fetch_era5_single_levels. No exclusions or specific use cases are provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/leandroavl/SMI_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server