Vertical Weather

Get an atmospheric profile

get_atmospheric_profile

Read-only

Wind, temperature, pressure, humidity and air density at chosen heights above a point.

    Each level has wind_u_ms (towards east), wind_v_ms (towards north), wind_speed_ms,
    wind_direction_deg (where the wind comes FROM, clockwise from north; 0 at zero speed
    means calm), temperature_k, pressure_pa, specific_humidity_kg_kg, relative_humidity_pct
    and density_kg_m3. valid_time is the model time actually used; provenance names the
    GFS run and grid point. Heights outside the model column are refused with the range
    that is available.

Input Schema

TableJSON Schema

Name	Required	Description
`time`	Yes	ISO 8601 timestamp with a timezone, e.g. 2026-10-03T18:00:00Z. Up to 14 days ahead or about ten days back.
`latitude`	Yes	Decimal degrees, north positive.
`longitude`	Yes	Decimal degrees, east positive.
`altitudes_m`	Yes	1 to 32 different heights in metres.
`altitude_reference`	Yes	agl: heights above ground level. msl: heights above mean sea level.
`ground_elevation_m_msl`	No	Optional site elevation in metres above sea level, used for agl heights instead of the model's terrain.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 26, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description adds value by detailing output fields, error behavior (heights outside the model column are refused with the available range), and provenance info (GFS run and grid point). No contradiction with annotations.

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 well-structured with a clear summary sentence followed by a detailed field explanation. It is appropriately sized for the complexity, though the field list is slightly verbose, it remains front-loaded and informative.

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 output schema exists and the schema covers parameters, the description adds necessary context about output fields and error handling. It is complete enough for an agent to call correctly, with no missing critical information.

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 does not add significant parameter semantics beyond the schema; it focuses on output fields rather than input parameters, and the schema already thoroughly documents each parameter.

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 clearly states the tool returns atmospheric variables (wind, temperature, pressure, humidity, density) at specified heights above a point. It is specific and distinguishes from sibling tools (get_capabilities, get_usage) by its focus on vertical profiles, leaving no ambiguity about what it does.

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 explains what the tool does but does not explicitly state when to use it versus alternatives or any prerequisites. It implies usage for obtaining atmospheric profiles but lacks exclusions or alternative routing, leaving the agent to infer context.

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

All Vertical Weather tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?