Skip to main content
Glama

fetch_era5_hourly_single_levels

Retrieve ERA5 hourly surface data for any date and location. Provide variable, year, month, day, and local output filename; optional bounding box restricts the download to a specific region.

Instructions

Downloads ERA5 hourly surface data.

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_single_levels('2m_temperature', '2023', '01', '15', 'temp_2023_01_15.nc') fetch_era5_hourly_single_levels('total_precipitation', '2023', '01', ['01','02','03'], 'precip_jan_1_3.nc', north=44, west=-10, south=36, east=4)
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 surface variable to download (e.g., '2m_temperature', 'total_precipitation')
output_filenameYesThe local filename for the downloaded data (e.g., 'data/raw/2m_temp_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?

No annotations are present, so the description must carry the burden of disclosing side effects. It only says 'Downloads' and does not mention that it writes a local file (output_filename), requires CDS credentials, or imposes API/rate limits. This leaves the agent with little beyond the action verb.

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 description is a single front-loaded sentence with no filler. It loses one point for being terse to the point of under-specification for a tool with nine parameters.

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?

With nine parameters, a rich schema, and multiple sibling tools, a one-sentence description is not complete enough. It omits when to use this tool, how output is delivered, and any operational caveats, despite the schema covering parameters well.

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 all nine parameters have descriptions and examples. The tool description adds no parameter-level meaning, so it does not exceed the baseline of 3.

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 the specific verb 'Downloads' and names a clear resource, 'ERA5 hourly surface data,' which distinguishes this from sibling pressure-level and soil-moisture tools. The 'hourly surface' qualifier disambiguates from fetch_era5_single_levels and fetch_era5_pressure_levels.

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?

The description provides no guidance about when to choose this tool over siblings such as fetch_era5_single_levels or fetch_era5_hourly_pressure_levels. It neither states explicit conditions nor mentions alternatives or exclusions.

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