Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Analyze Design

analyze_design

Runs AEDT design analyses with configurable project, design, and setup targets, plus HPC options for cores, GPUs, tasks, batch solves, and background execution.

Instructions

Run analysis on an AEDT design.

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

Input Schema

NameRequiredDescriptionDefault
machineNoTarget machine name for remote or batch solves.localhost
acf_fileNoFull path to a custom ACF file for HPC configuration.
num_gpusNoNumber of GPUs to use for analysis.
num_coresNoNumber of CPU cores to use for analysis.
num_tasksNoNumber of HPC tasks to use for analysis.
setup_nameNoName of the setup to analyze. If ``None``, all setups in the target design are analyzed.
design_nameNoName of the design to analyze. If ``None``, the active design is used.
project_nameNoName of the project to analyze. If ``None``, the active project is used.
run_in_threadNoWhether to submit the batch solve in a background thread.
solve_in_batchNoWhether to solve the design in batch mode.
use_auto_settingsNoWhether to use automatic HPC settings when supported.
analyze_all_designsNoWhether to analalyze all designs. When ``True``, ``Desktop.analyze_all`` is called for the target project/design. This analyzes all setups in a design or all designs in a project.
revert_to_initial_meshNoWhether to revert to the initial mesh before solving.

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, but it only says 'run analysis'. It does not disclose that this is a potentially long-running compute operation, whether it mutates results, whether it blocks, or what happens when defaults are used.

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?

It is a single short sentence with no wasted wording and is front-loaded. Its brevity is efficient, though the same brevity leaves necessary context unstated elsewhere.

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 13-parameter analysis tool with no annotations, the description is far too thin. It omits prerequisites, default resolution behavior for project/design/setup, batch and HPC implications, and what the operation changes.

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 schema already documents all 13 parameters in detail. The description adds no meaning beyond the schema, which meets the baseline of 3 for high-coverage schemas.

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: running analysis on an AEDT design. It is clear enough for a domain agent to know this triggers simulation/solve, but it does not distinguish itself from siblings such as validate_design or create_design.

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 exclusions, and no mention of prerequisites such as being connected to AEDT or having the target design open. The agent must infer all usage context from the tool name and schema.

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