Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

List Designs

list_designs

Retrieve open AEDT projects and their designs from a connected instance, optionally filtering results to a single project by name.

Instructions

List projects and designs for the connected AEDT instance.

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

Input Schema

NameRequiredDescriptionDefault
project_nameNoOptional project name to limit the response to a single project. If``None``, all open projects and their designs are returned.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/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 burden, and "List" plus "connected instance" implies a non-destructive read requiring an existing AEDT session. It does not state behavior when no instance is connected (error vs. empty result) or whether only open projects are visible, leaving real gaps for a no-annotation tool.

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, front-loaded sentence with no wasted wording. It is efficient, though it packs two resources into one phrase without clarifying the nesting (designs belong to projects), which slightly reduces precision.

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?

The tool is simple with one optional parameter and a full output schema, so return values need not be explained. However, for a connection-dependent tool with no annotations, the description should at minimum state the precondition or the failure mode, which it does not.

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 schema already documents project_name as an optional filter with its None default. The description adds nothing about this filter, so the baseline of 3 applies when the schema does the heavy lifting.

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 ("List") and resources ("projects and designs") scoped to the connected AEDT instance. It is clearly distinguishable from mutation siblings like create_design or save_project, though it does not explicitly contrast with list_projects.

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?

Provides no when-to-use guidance, no exclusions, and does not mention list_projects as the alternative when only projects are needed. The only contextual hint is the phrase "connected AEDT instance," which implies a connection must exist first, but this is left to inference.

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