Skip to main content
Glama
Sign In
profili-mcp

profili-mcp

by GaillumXc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Get Polar

get_polar

Retrieve stored airfoil polar data (CL/CD/CM vs. angle of attack) at the Reynolds number closest to a specified value.

Instructions

Get the stored polar (CL/CD/CM vs alpha, degrees) at the Reynolds number closest to re.

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

Input Schema

NameRequiredDescriptionDefault
reYes
nameYes
install_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/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 but does disclose the key non-obvious behavior: selection is by nearest Reynolds number rather than exact match, which prevents wrong assumptions about results. It omits whether the value is interpolated or a stored snapshot, what happens when 'name' matches nothing, and whether the call is a pure read.

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 unit clarification '(degrees)' earns its place by disambiguating alpha.

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 not be described, and the nearest-match rule is captured. But for a three-parameter tool with zero schema coverage and no annotations, the meaning of 'name' and 'install_dir' plus failure behavior are real gaps.

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 only partially does: it explains that 're' is a Reynolds number used for nearest-match lookup. It never clarifies whether 'name' is the airfoil name or the polar name (ambiguous given the list_polars and find_airfoils_by_polar siblings), and 'install_dir' is left entirely unexplained.

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 ('Get the stored polar') and even expands what a polar contains (CL/CD/CM vs alpha, degrees), which an agent could not infer from the name alone. It implicitly distinguishes itself from list_polars by returning data rather than a listing, though it never names that sibling.

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?

The word 'stored' implies a precondition — only polars already computed/persisted can be fetched — which is useful usage context. However, there is no explicit guidance on when to use this versus list_polars or find_airfoils_by_polar, and no statement of what to do when no polar exists.

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