Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Open Project

open_project

Opens an Ansys Electronics Desktop (AEDT) project from a full file path and optionally activates a specified design, enabling work in the correct project context.

Instructions

Open an AEDT project.

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": {
      "project_path": "<project_path>"
    },
    "name": "open_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_nameNoName of the design to activate after opening. If ``None``, the first design is used
project_pathYesFull path to the AEDT project file.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It says nothing about failure modes (missing file, invalid path), whether an already-open project is replaced, what state changes occur, or whether permission/locking constraints apply; only the presence of an output schema offsets the return-value gap.

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 short sentence with zero padding, and the action is front-loaded. Its brevity is efficient rather than padded, though it borders on under-specification for the amount of behavior an agent needs to know.

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?

For a state-mutating operation that loads a project into an application, the definition is too thin: prerequisites, side effects, and interactions with AEDT session state are all unstated. The output schema covers the return value, but the operational context an agent needs to call this correctly is missing.

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

Parameters3/5

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

Schema description coverage is 100%, so both parameters (project_path and design_name) are already fully documented in the schema, including the design_name default behavior. The description adds nothing beyond this, which meets the baseline of 3 when the schema does the work.

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: 'Open' plus 'AEDT project'. An agent knows what action is taken, but the description offers no differentiation from siblings such as launch_aedt, connect_to_aedt, or create_design, so the boundary between opening a project and those operations is left implicit.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. The description does not say whether AEDT must already be running, whether the project must exist, or how this differs from connecting to an existing session.

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