profili-mcp

Overview Schema Source Related Servers Discussions Admin

Import Airfoil Dat

import_airfoil_dat

Imports .dat airfoil coordinate files into a Profili library, with optional backup and restart guidance for running instances.

Instructions

Import a .dat coordinate file into the Profili library. The database is backed up first unless backup=False. Restart Profili afterwards if it was already running.

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": {
      "file_path": "<file_path>"
    },
    "name": "import_airfoil_dat"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No
`note`	No
`backup`	No
`library`	No
`file_path`	Yes
`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.3/5.0

Behavior3/5

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

With zero annotations the description carries the full behavioral burden, and it does disclose two real traits: a database backup is taken unless backup=False, and Profili must be restarted if already running. It omits the most important mutation risk for an import tool — whether an existing airfoil of the same name is overwritten, and what happens on malformed .dat files.

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?

Three short sentences, front-loaded with the core action, then the two operational caveats. Nothing is redundant and nothing pads the definition.

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?

An output schema exists, so return values need no explanation, and the backup/restart notes cover operational side effects. However, for a write-into-library tool with no annotations and 0% schema coverage on six parameters, the definition should say what happens to a name collision and what library/install_dir control.

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 description coverage is 0% across six parameters, and the description only illuminates two of them: file_path (a .dat coordinate file) and backup (default true, backup taken first). The meaning of name, note, library (an integer index into what?), and install_dir is left entirely to guesswork, which is a substantial gap for a 6-param tool.

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: 'Import a .dat coordinate file into the Profili library.' An agent can distinguish this from export_airfoil_dat or list_libraries directly from the wording. It stops short of naming the inverse/sibling operation explicitly, but the purpose is unambiguous.

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?

Usage is implied by the resource described (loading external coordinate files into the library), and the restart note gives operational context for when follow-up action is needed. There is no explicit when-to-use-versus-alternatives guidance, no prerequisites (e.g. whether Profili must be closed), and no exclusions.

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

Deploy Server