Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Get Model Info

get_model_info

Retrieve information about the active or named design in Ansys Electronics Desktop to inspect model details, using the active design when no name is supplied.

Instructions

Get information about the current model/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": "get_model_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
design_nameNoName of the design to get information for. If ``None``, the active design is used.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/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 burden. "Get" weakly implies a read operation, but it doesn't state whether an AEDT session must already be connected, whether it errors when no active design exists, or what happens with an invalid design_name — all relevant for a tool that depends on external application state.

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 no filler and the resource stated up front. It is efficient, though its brevity is partly the source of the vagueness noted 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?

An output schema exists, so return values needn't be explained, but the description never indicates what kind of information the tool yields (units, dimensions, material, solver settings) nor the connection state required. For a tool whose whole value is its returned content, that omission leaves the agent unable to predict whether calling it answers its question.

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 coverage is 100% and the single optional design_name parameter is fully documented in the schema, so baseline 3 applies. The description's phrase "current model/design" loosely reinforces the default-to-active-design behavior but adds nothing the schema lacks.

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

Purpose3/5

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

The description pairs a generic verb ("Get") with a vague resource ("information about the current model/design"). It doesn't say what information is returned or how this differs from siblings like analyze_design or list_designs, so the agent knows the topic but not the payload.

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?

No guidance on when to use this versus analyze_design, validate_design, or list_designs, and no prerequisites (e.g., whether a connection or active design is required) are mentioned. The agent must infer everything from the name alone.

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