Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Export Config

export_config

Export the active design configuration to a JSON file, with optional project, design, output path, and overwrite settings for saving or sharing setup data.

Instructions

Export the active design configuration as a JSON file.

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

Input Schema

NameRequiredDescriptionDefault
designNoDesign to export configuration from.
outputNoPath to output the JSON file to. If ``None``, the configuration is exported to a temporary file and returned inline.
projectNoProject containing the design to export.
overwriteNoWhether to overwrite an existing configuration file.

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?

With no annotations, the description carries the full disclosure burden and falls short: it does not say whether an AEDT connection is required, that the tool writes to disk and can overwrite an existing file, or what happens when no design is active. The only behavioral cue is the phrase 'active design', and it does not explain side effects or failure modes for a file-writing operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with zero waste, but for a four-parameter, annotation-free tool the brevity reflects under-specification rather than tight editing. It is structurally clean but too thin to earn a high score.

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

Completeness3/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 described, and the schema documents all four parameters. However, with no annotations the description should cover prerequisites and write/overwrite side effects, which it omits, leaving a real gap for a disk-writing tool.

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% (design, project, output, overwrite all documented), so the baseline is 3. The description adds little beyond the schema and its 'active design' phrasing is loosely at odds with the optional design/project selectors, adding no real semantic clarity.

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?

Names a specific verb (Export) and resource (active design configuration) plus the output format (JSON file), so the agent knows exactly what the tool does. It does not distinguish itself from siblings like export_results, so it stops short of a 5.

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 statement of when to use this tool versus alternatives, no prerequisites (e.g., needing a connected/active AEDT session), and no exclusions. The agent must infer everything about selection context.

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