Skip to main content
Glama

takeoff_performance

Calculate takeoff field length and V-speeds based on aircraft weight, altitude, temperature, wind, and runway conditions for flight planning.

Instructions

Calculate takeoff field length and V-speeds.

Uses simplified performance equations for educational purposes.

Args: weight_kg: Takeoff weight in kg pressure_altitude_ft: Airport pressure altitude in feet temperature_c: Outside air temperature in Celsius wind_kts: Headwind (+) or tailwind (-) in knots runway_slope_pct: Runway slope in percent (+ uphill) runway_condition: "dry", "wet", or "contaminated" thrust_to_weight: Thrust-to-weight ratio cl_max_takeoff: Maximum lift coefficient in takeoff config wing_area_m2: Wing reference area in m² cd0: Zero-lift drag coefficient oswald_e: Oswald efficiency factor aspect_ratio: Wing aspect ratio

Returns: Formatted string with takeoff performance calculations including V-speeds, ground roll, air distance to 35 ft, and factored distances.

Raises: No exceptions are raised directly; errors are returned as formatted strings.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
weight_kgYes
pressure_altitude_ftYes
temperature_cYes
wind_ktsNo
runway_slope_pctNo
runway_conditionNodry
thrust_to_weightNo
cl_max_takeoffNo
wing_area_m2No
cd0No
oswald_eNo
aspect_ratioNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description discloses that it uses simplified equations for education and that errors are returned as strings, but lacks details on limitations or side effects. No annotations exist to contradict or support.

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 purpose line, Args list, Returns, and Raises. Each sentence is informative, though the Args list could be slightly more integrated.

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?

Covers input, output (formatted string), and error handling. With an output schema present, the return format is sufficient. Minor gap: lacks units for output V-speeds or specific performance assumptions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description provides a full Args list with clear, concise meanings for all 12 parameters (e.g., 'Takeoff weight in kg'), fully compensating for the schema gap.

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 'Calculate takeoff field length and V-speeds' which is a specific verb+resource. It distinguishes from siblings like 'landing_performance' by specifying takeoff.

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 mentions 'for educational purposes' implying a use case but does not explicitly state when to use this tool vs alternatives like 'get_aircraft_performance' or 'landing_performance'. No exclusions or alternatives 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/cheesejaguar/aerospace-mcp'

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