Skip to main content
Glama
LaplaceYoung

ansys-aedt-mcp

by LaplaceYoung

aedt_environment

Inspect Python and PyAEDT availability before launching AEDT to confirm simulation environment is ready.

Instructions

Inspect Python and PyAEDT availability without launching AEDT.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior3/5

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

Notes that it does not launch AEDT, which is a key behavioral trait, but no annotations are provided to cover safety or side effects. Lacks details on what 'inspect' entails exactly (e.g., return format, error handling).

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?

Single sentence that is front-loaded with the key action and resource. No unnecessary words; every part earns its place.

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 environment-check tool, the description is adequate but lacks specification of what the output contains (though output schema exists but not shown). Could benefit from noting that it returns availability status.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist, so schema coverage is 100%. Description does not need to add param info; baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Describes a specific action (Inspect) on a clear resource (Python and PyAEDT availability) without launching AEDT, distinguishing it from sibling tools that require an active session.

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?

Implies a preliminary check before using other tools, but does not explicitly state when to use or not use, nor mention alternatives. Lacks explicit guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LaplaceYoung/ansys-aedt-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server