Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Clear Aedt

clear_aedt

Closes all open AEDT projects to reset application state for a new session or workflow.

Instructions

Clear the AEDT state by closing all projects.

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

Input Schema

NameRequiredDescriptionDefault
close_projectsNoWhether to close all open projects.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 burden of behavioral disclosure. It implies a destructive action (closing all projects) but never warns about unsaved work, whether it saves first, or what permissions/connection state are required.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler; the verb and the mechanism of clearing state are stated immediately.

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 (one optional boolean) and an output schema exists, so return values needn't be explained. However, for a state-clearing operation with no annotations, a warning about unsaved projects or the resulting connection state is a meaningful omission.

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 close_projects is fully documented in the schema, establishing the baseline of 3. The description's phrase 'closing all projects' mildly reinforces the default behavior but adds no syntax or edge-case detail.

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: 'Clear the AEDT state by closing all projects.' An agent can understand the operation without opening the schema, though it doesn't distinguish itself from siblings like disconnect_from_aedt or save_project.

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?

No when-to-use guidance, prerequisites, or alternatives are given. The description doesn't say when clearing state is appropriate versus simply disconnecting, nor whether projects must be saved first.

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