Skip to main content
Glama

Find Airfoils By Polar

find_airfoils_by_polar

Search airfoils by aerodynamic performance at a given Reynolds number and angle of attack, then filter results by lift, drag, and lift-to-drag criteria.

Instructions

Search airfoils by aerodynamic performance at one operating point.

Narrows by name prefix first (the polar table is huge), then evaluates the polar at alfa (linear interpolation) and applies the criteria.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name_prefix": "<name_prefix>",
      "re": "<re>",
      "alfa": "<alfa>"
    },
    "name": "find_airfoils_by_polar"
  }
}

Input Schema

NameRequiredDescriptionDefault
reYes
alfaYes
limitNo
max_cdNo
min_clNo
install_dirNo
name_prefixYes
min_cl_over_cdNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the two-stage strategy: name-prefix prefiltering because the polar table is huge, then linear interpolation at alfa. It does not mention read-only nature, permissions, rate limits, pagination, or how the criteria are combined.

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?

Two tight sentences, with purpose front-loaded and implementation detail second. Every clause adds information and there is no filler.

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?

Given 8 parameters, 0% schema descriptions, and no annotations, the description is too thin: it omits what re means, how the criteria parameters interact, and usage alternatives. Output schema exists, so return values need not be explained, but the input side is incomplete.

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

Parameters2/5

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

Schema coverage is 0% across 8 parameters, and the description explains only name_prefix and alfa; it gestures at 'criteria' without mapping max_cd, min_cl, min_cl_over_cd, or re. The remaining parameters, limit and install_dir, are undocumented. Marginal help over the bare schema.

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

Purpose4/5

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

States a specific verb and resource ('search airfoils by aerodynamic performance') plus the operating-point scope. It does not distinguish this tool from sibling search_airfoils or get_polar, so an agent must infer when this is preferable. Clear but lacks sibling differentiation.

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 the tool is for filtering airfoils by polar performance at a single alfa, but gives no explicit when-to-use, when-not, or alternative tools such as search_airfoils or get_polar. It also states no prerequisites or exclusions.

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