Tigl FAQs

Question 1

What are the key benefits of using Tigl for developers?

Accepted Answer

Developers benefit from Tigl's deterministic CPACS/TiGL stand-ins, which ensure stable local development and CI without requiring native geometry runtimes. It also offers a curated set of CPACS lifecycle tools and Pydantic-backed validation for robust workflow management.

Question 2

What is Tigl and its primary purpose?

Accepted Answer

Tigl is a lightweight Model Context Protocol (MCP) server specifically designed to facilitate CPACS-oriented TiGL workflows. Its main purpose is to provide deterministic, JSON-friendly tooling with stubbed CPACS/TiGL behavior for stable local development, testing, and CI environments.

Question 3

What transport options are available for the Tigl server?

Accepted Answer

Tigl's FastMCP-powered server supports multiple transport options, including standard I/O (stdio) for command-line interaction and HTTP-compatible transports for more flexible, non-blocking server configurations.

Question 4

What kind of CPACS-related tools does Tigl offer?

Accepted Answer

Tigl provides a curated set of tools for various CPACS lifecycle aspects, including inspection, export, sampling, and parameter management. These tools are designed to work seamlessly within a deterministic and easily testable MCP environment.

Question 5

Does Tigl provide full native TiGL geometry fidelity?

Accepted Answer

No, Tigl intentionally uses simplified geometry values that reflect a stub contract rather than full native TiGL fidelity. This focus on deterministic stand-ins is for stable development and testing of workflows, not for precise geometry computations.

Tigl

Tigl

主な機能

ユースケース

主な機能

ユースケース