Skip to main content
Glama
Sign In
profili-mcp

profili-mcp

by GaillumXc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

List Libraries

list_libraries

Lists airfoil libraries defined in the Profili database to help AI agents discover available datasets before searching or editing airfoil data.

Instructions

List airfoil libraries defined in the Profili database.

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

Input Schema

NameRequiredDescriptionDefault
install_dirNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. 'List' implies a read-only operation, but the description does not say whether Profili must be running, whether results are scoped to an installation, or how the database is accessed.

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?

The description is a single front-loaded sentence with no wasted words. It is concise, although that conciseness contributes to the missing parameter and usage detail.

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?

The output schema reduces the need to describe return values, but the definition remains incomplete for a tool with an optional installation-path parameter and no annotations. It omits the parameter's purpose and the execution context required to call it correctly.

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?

The tool has one optional parameter, 'install_dir', with 0% schema description coverage. The description does not mention this parameter at all, so it fails to compensate for the missing schema semantics. The output schema exists and need not be explained, but the input parameter remains 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?

The description states a specific verb and resource: 'List airfoil libraries defined in the Profili database.' This is clearer than a tautology and distinguishes the tool from sibling analysis tools. It does not explicitly distinguish it from 'list_polars', but the resource noun is specific enough.

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?

The description gives no guidance on when to use this tool versus alternatives such as 'list_polars' or 'search_airfoils'. It implies a listing operation but provides no conditions, exclusions, or prerequisites.

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