Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Disconnect From Aedt

disconnect_from_aedt

Detach the MCP session from the AEDT instance and release its resources, choosing to keep the AEDT window open or close the desktop and projects.

Instructions

Disconnect from the AEDT instance.

This tool detaches the MCP session from the AEDT instance and releases associated resources. It can either keep the AEDT window open or close the AEDT desktop entirely.

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

Input Schema

NameRequiredDescriptionDefault
close_desktopNoWhether to close the AEDT desktop on disconnect. Set to ``False`` to keep the AEDT window open after detaching the MCP session. When ``None``, the tool asks the caller to choose before disconnecting.
close_projectsNoWhether to close all open projects before disconnecting.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does disclose that the session detaches and resources are released, and that the desktop or open projects may be closed. It omits important behavior such as what happens when no connection exists, whether the action is reversible without reconnecting, and any confirmation/error semantics for the None case (left to the schema).

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?

Three short sentences with the action front-loaded and the optional behavior second. There is minor redundancy between 'Disconnect from the AEDT instance' and 'detaches the MCP session from the AEDT instance,' but nothing is wasted overall.

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

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter teardown tool with full schema coverage and an output schema, the description covers purpose and the two shutdown modes adequately. The main gap is lifecycle context (preconditions and post-disconnect state), which would be helpful given the absence of annotations.

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%, so both close_desktop and close_projects are fully documented in the schema, including the None prompt behavior. The description only restates the high-level choice between keeping the window open and closing the desktop, adding no syntax or interaction detail beyond the structured fields; baseline 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 ('Disconnect from the AEDT instance') and clarifies the mechanism ('detaches the MCP session ... and releases associated resources'). It is clearly the inverse of connect_to_aedt without naming it, so an agent can route correctly, though it does not explicitly contrast with siblings like clear_aedt or check_aedt_status.

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 implied by the tool's name and by the mention of keeping the window open versus closing the desktop, but there is no explicit when-to-use guidance, no prerequisites (e.g., must be connected first), and no statement of what to use instead for clearing state or reconnecting. The caller is left to infer the situation.

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