profili-mcp

Overview Schema Source Related Servers Discussions Admin

Analyze Airfoil

analyze_airfoil

Computes a viscous airfoil polar using bundled XFOIL and optionally saves results to the Profili library for GUI access.

Instructions

Compute a fresh viscous polar with the bundled XFOIL (same recipe as Profili's own solver). If save_to_db=True the result is written into the Profili library and appears in the GUI after restart.

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": "<name>"
    },
    "name": "analyze_airfoil"
  }
}

Input Schema

Name	Required	Description	Default
`re`	No
`mach`	No
`name`	Yes
`ncrit`	No
`backup`	No
`alfa_end`	No
`alfa_step`	No
`alfa_start`	No
`save_to_db`	No
`install_dir`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 15, 2026

TDQS

B3/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two valuable traits: the computation is fresh rather than cached, and save_to_db persists into the Profili library with visibility only after a GUI restart. It omits whether XFOIL execution is slow, can fail, or what permissions/paths install_dir requires.

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?

Two tight sentences with the core action front-loaded and the persistence caveat second. The parenthetical about Profili's solver earns its place as disambiguation; nothing is padded.

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

Completeness3/5

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

The existence of an output schema relieves it of explaining return values, and it covers the write side effect. However, for a 10-parameter computational tool with zero schema descriptions and no annotations, the definition leaves the agent under-informed about most inputs and about failure/runtime behavior.

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 10 parameters, so the description must compensate, but it only explains save_to_db. Key inputs such as re, mach, ncrit, alfa_start/step/end, backup, and install_dir get no meaning beyond their names and defaults.

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: 'Compute a fresh viscous polar with the bundled XFOIL.' The word 'fresh' and the reference to the bundled solver distinguish it from reading an existing polar, though it does not explicitly contrast with the sibling analyze_naca.

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 guidance on when to choose this over analyze_naca, get_polar, or find_airfoils_by_polar, and no prerequisites such as installing XFOIL or required airfoil data. The only conditional behavior mentioned is save_to_db, which is a side-effect note rather than usage routing.

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

Deploy Server