Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Screenshot

screenshot

Captures the current AEDT design view—model, field plot, or mesh—and saves it as a 1080p or 4K image to a specified path.

Instructions

Capture a screenshot of the current AEDT design view.

This tool captures the current design preview as an image. It supports model views, field plots, and mesh visualizations, depending on what's currently displayed in AEDT.

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

Input Schema

NameRequiredDescriptionDefault
pathNoOutput image path.screenshot.jpg
designNoDesign to capture. If ``None``, the active design is used.
projectNoProject containing the design to capture. If ``None``, the active project is used.
plot_typeNoType of screenshot. Options are ``"model"``, ``"field"``, and ``"mesh"``.model
resolutionNoImage resolution. ``"1080p"`` exports a 1920 x 1080 image, while ``"4k"`` exports a 3840 x 2160 image.1080p
open_viewerNoWhether to open the saved screenshot in the system image viewer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral burden. It discloses which view types can be captured, but omits the key side effects an agent needs: that an image file is written to disk at the given path (and whether it overwrites), that a viewer window may pop up, and that a live AEDT connection is required.

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?

Two short, front-loaded sentences with no filler. The second sentence partially restates the first ("captures ... as an image"), which is mild redundancy, but the supported-view detail is new information.

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?

For a six-parameter tool with no annotations and no output schema, the description should mention the mandatory live-session precondition and the file-write side effect. It covers what the tool produces visually but leaves an agent guessing about the operational environment and on-disk behavior.

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 every parameter including defaults and enums is already documented in the schema. The description adds no parameter-level meaning, which is acceptable at full coverage but earns only the baseline.

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?

States a specific verb and resource ("Capture a screenshot of the current AEDT design view") and enumerates the visual modes covered (model, field plots, mesh). No sibling tool competes for this function, so the purpose is unambiguous even without an explicit contrast.

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?

Usage is only implied: the second sentence explains that the output depends on what is currently displayed, which hints at when the tool applies. There is no statement of prerequisites (an active AEDT session/project/design must exist) or of when not to use it.

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