Skip to main content
Glama
Sign In
profili-mcp

profili-mcp

by GaillumXc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Airfoil Geometry

get_airfoil_geometry

Retrieve an airfoil's metadata and full coordinates, including chord fractions from leading to trailing edge for both surfaces, to support geometry inspection and analysis.

Instructions

Get an airfoil's metadata + full coordinates (chord fractions, LE->TE for both surfaces).

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

Input Schema

NameRequiredDescriptionDefault
nameYes
install_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the shape of the returned data (metadata plus full coordinates, both surfaces, LE->TE), which is genuine behavioral context beyond the name, but it says nothing about lookup failure behavior, which library is searched, or whether the call is side-effect free. An output schema exists, so not explaining return formatting is acceptable.

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?

A single compact sentence with the resource front-loaded and the parenthetical qualifying the returned data rather than padding it. The 'LE->TE' shorthand is slightly cryptic but efficient for the domain.

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?

For a simple two-parameter getter with an output schema and no annotations, the description covers the essential purpose and return content. The unaddressed 'install_dir' parameter and absent guidance on lookup scope leave a moderate but not fatal gap.

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%, so the description must compensate, and it largely does not. The possessive 'an airfoil's' hints that 'name' identifies the airfoil, but the 'install_dir' parameter is never mentioned or explained, leaving the agent to guess what it controls (library/directory selection) and when to supply it.

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 ('Get') and resource (an airfoil's metadata plus full coordinates) and further specifies what the coordinates contain: chord fractions, ordered LE->TE for both surfaces. This is enough to distinguish it from analysis-oriented siblings like analyze_airfoil or search_airfoils, though it never explicitly contrasts itself with them.

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 call this versus alternatives such as analyze_airfoil or export_airfoil_dat, and no mention of prerequisites (e.g., whether the airfoil must already exist in a library). The agent must infer usage from the name and the returned content alone.

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