Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Create Design

create_design

Create a new design in Ansys Electronics Desktop (AEDT) for a chosen application type (HFSS, Maxwell, Q3D, Icepak, Circuit) and optionally set the project, design name, and solution type.

Instructions

Create a new design in AEDT.

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": {
      "app_type": "<app_type>"
    },
    "name": "create_design"
  }
}

Input Schema

NameRequiredDescriptionDefault
app_typeYesAEDT application type. Options are ``"Hfss"``, ``"Maxwell2d"``, ``"Maxwell3d"``, ``"Q3d"``, ``"Q2d"``, ``"Icepak"``, ``"Circuit"``, ``"TwinBuilder"``, ``"Mechanical"``, ``"Emit"``, ``"RMXprt"``, and ``"Hfss3dLayout"``.
design_nameNoName for the new design. If ``None``, an auto-generated name is used.
project_nameNoProject to create design in. If ``None``, the active project is used.
solution_typeNoSolution type for the design (app-specific).

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 provided, so the description carries the full behavioral burden. "Create" implies a mutation, but the description does not disclose side effects, required AEDT connection state, behavior when the design already exists, or how the active project is selected when project_name is omitted.

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, though its brevity contributes to gaps addressed under contextual completeness rather than to structural clutter.

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 creation tool with four parameters and no annotations, the description is too thin. Although an output schema exists, the definition still omits essential context such as connection requirements, active-project fallback behavior, and what happens when a design name is duplicated.

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 the input schema already documents app_type, design_name, project_name, and solution_type in detail. The description adds no additional parameter meaning beyond the schema baseline.

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: "Create a new design in AEDT." This clearly identifies the operation, but it does not distinguish the tool from adjacent siblings such as list_designs, open_project, or launch_aedt beyond the basic act of creation.

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 guidance on when to use this tool versus alternatives, no prerequisites such as an active AEDT connection or project, and no exclusions. The agent must infer all usage conditions from the name and schema.

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