Skip to main content
Glama

fetch_era5_hourly_pressure_levels

Download ERA5 hourly atmospheric variables at specified pressure levels into a local NetCDF file.

Instructions

Downloads ERA5 hourly data on specific pressure levels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dayYesThe day(s) for the data (e.g., '15' or ['01','02','03'])
eastNoEastern longitude (e.g., 20 for 20E) Example: fetch_era5_hourly_pressure_levels('temperature', 850, '2023', '01', '15', 'temp_850hpa_2023_01_15.nc') fetch_era5_hourly_pressure_levels('geopotential', 500, '2023', '01', '15', 'z500_europe.nc', north=70, west=-25, south=30, east=40)
westNoWestern longitude (e.g., -10 for 10W)
yearYesThe year for the data (e.g., '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', 'u_component_of_wind')
pressure_levelYesThe pressure level in hPa (e.g., 500, 850, 1000)
output_filenameYesThe local filename for the downloaded data (e.g., 'data/raw/geopotential_850hpa_2023_01_15.nc')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states the download action, without disclosing whether existing files are overwritten, network dependencies, data size implications, or any side effects beyond creating a file.

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, front-loaded sentence with no filler; every word adds meaning. It is appropriately sized for the simple action it names and avoids redundancy.

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

Completeness2/5

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

Despite rich schema coverage, the tool has 10 parameters, no annotations, and an output schema, yet the description offers no context on prerequisites, when to use it, or caveats. The one-sentence description is too minimal to fully support selection and invocation in context.

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%, and each parameter has descriptive text with examples (e.g., 'east' includes full usage examples). The tool description itself adds no parameter semantics, but the schema fully covers them, so the baseline score applies.

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 names the resource ('ERA5 hourly data on specific pressure levels'), which clearly differentiates it from sibling tools like fetch_era5_single_levels and fetch_era5_pressure_levels by specifying both hourly and pressure level dimensions.

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?

No usage guidance is provided. It does not state when to choose this over fetch_era5_pressure_levels or fetch_era5_hourly_single_levels, nor mention prerequisites like CDS authentication, optional bounding-box usage, or the ability to specify multiple days.

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