Skip to main content
Glama
Sign In
profili-mcp

profili-mcp

by GaillumXc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Launch Profili

launch_profili

Start the Profili GUI to open the legacy airfoil design application for managing profiles, polar data, and analyses.

Instructions

Start the Profili GUI.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "launch_profili"
  }
}

Input Schema

NameRequiredDescriptionDefault
install_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden for a side-effecting operation that spawns an external GUI process. It says nothing about whether the call blocks, what happens if an instance is already running, what occurs if Profili is not installed, or what the return indicates.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single sentence is front-loaded and free of padding, but this is terseness rather than effective concision — it omits information the agent needs rather than trimming what is unnecessary.

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 explained, but for a process-launching tool with an undocumented parameter and no annotations the definition leaves significant gaps around preconditions and failure modes.

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% for the single optional install_dir parameter, and the description does not compensate. An agent has no idea whether install_dir is a root folder, an executable path, or how the tool behaves when it is omitted.

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 states a specific verb and resource ('Start the Profili GUI'), which is unambiguous and distinguishes it from the sibling close_profili by polarity. It stops short of any explicit sibling differentiation, but the action is clear enough to act on.

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 launch versus when not to (e.g., if the GUI is already running), no prerequisites, and no mention of close_profili as the paired teardown. The agent must infer all of this.

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