Skip to main content
Glama
Sign In
profili-mcp

profili-mcp

by GaillumXc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Export Airfoil Dat

export_airfoil_dat

Exports an airfoil from the library to a Profili .dat coordinate file for use in airfoil design and analysis workflows.

Instructions

Export an airfoil from the library to a Profili .dat coordinate file.

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": "export_airfoil_dat"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
install_dirNo
output_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full behavioral burden. It reveals only that a file is written; it says nothing about overwrite behavior for an existing .dat file, permission requirements, whether the export is derived from the selected Profili library, or what happens on failure.

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?

A single front-loaded sentence with no filler; the verb, source, and destination format come in immediate order. Nothing in it is redundant or wasteful, even though it is sparse.

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?

An output schema exists, so return values need not be described, but for a filesystem-writing export with three undocumented parameters and no annotations, the definition omits essential information. The relationship between install_dir and output_path and any overwrite/side-effect behavior are absent.

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 three parameters, so the description must compensate and does not. 'From the library' loosely hints that 'name' is a library airfoil identifier, but install_dir and output_path are entirely unexplained, including which one actually determines the file location.

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?

The description names a specific verb (export), the resource (an airfoil from the library), and the output artifact (a Profili .dat coordinate file), which implicitly separates it from the sibling import_airfoil_dat. It stops short of naming any sibling or stating the inverse-direction contrast explicitly, so it is clear but not fully differentiated.

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?

There is no guidance on when to choose this over import_airfoil_dat or other airfoil tools, and no stated preconditions such as whether Profili must be running or a library must be selected first. An agent must infer all usage context from the one-line purpose.

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

Deploy Server

Other Tools