Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Export Results

export_results

Export AEDT simulation results to a specified path as Touchstone, profile, convergence, or mesh data, optionally for a chosen setup.

Instructions

Export simulation results from 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": {
      "output_path": "<output_path>"
    },
    "name": "export_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
setup_nameNoSetup name for the export. If ``None``, the active setup is used.
export_typeNoType of export. Options are ``"touchstone"``, ``"profile"``, ``"convergence"``, and ``"mesh"``.touchstone
output_pathYesPath to export the results to.

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 burden and provides nothing beyond the one-line purpose. It does not say whether an existing file at output_path is overwritten, whether the export requires an active/valid setup, what the four export types produce, or what the tool returns. For a file-writing tool with no annotation coverage this is a substantial 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?

The single sentence is front-loaded with the verb and resource and contains no filler. It is efficient, though the brevity comes at the cost of the behavioral detail 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 need not be explained, but for a tool with a required output path and four export modes and zero annotations, the description leaves key operational questions unanswered: overwrite behavior, required session state, and where/how results are written. It is too thin relative to the tool's complexity.

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 the schema already documents setup_name fallback to the active setup, the four export_type values, and output_path. The description adds no meaning beyond that, so the baseline of 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 states a specific verb and resource: 'Export simulation results from AEDT.' An agent can tell this writes simulation results out of the AEDT session rather than manipulating the design or project. It does not, however, distinguish itself from the sibling export_config, so the boundary between the two is left unclear.

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 choose this tool over export_config or the other siblings, nor any mention of prerequisites such as an open project, active design, or a completed simulation run. The agent must infer all of that from context.

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