Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Validate Design

validate_design

Validate an Ansys Electronics Desktop design without starting a solve, checking the active or specified project/design for setup issues before simulation.

Instructions

Validate an AEDT design without starting a solve.

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

Input Schema

NameRequiredDescriptionDefault
design_nameNoName of the design to validate. If ``None``, the active design is used.
project_nameNoName of the project to validate. If ``None``, the active project is used.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and 'without starting a solve' is a genuine disclosure that the call is lightweight and non-solving. It does not say whether validation mutates design state, requires a connected AEDT session, how long it takes, or what failure looks like. Some value beyond the name, but far from full transparency for an unannotated tool.

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?

A single short sentence with the key constraint front-loaded and zero filler. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All parameters are optional and fully documented in the schema, and an output schema exists so return values need not be described. The main remaining gap is that with no annotations, the description could say more about session requirements and side effects.

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%, and both parameters already document their None-defaults meaning 'use the active design/project'. The description adds nothing about these parameters, so the baseline 3 applies.

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 names a specific verb (validate) and resource (an AEDT design) and adds a scope qualifier, 'without starting a solve,' that meaningfully separates it from heavier siblings such as analyze_design. It stops short of naming the alternative explicitly, so the differentiation is implied rather than stated.

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?

The phrase 'without starting a solve' implies this is a lightweight pre-solve check, which hints at when to use it. However, it never states when to prefer analyze_design instead, nor any prerequisites for validation to succeed, so guidance is only inferable.

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