Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Check Aedt Status

check_aedt_status

Check AEDT initialization status before connecting. Returns a hint to launch or connect when no session is active; when connected, returns version, projects, designs, and connection details.

Instructions

Check the status of AEDT initialization.

This tool is always reachable, even before a connection has been established. When no AEDT session is active, it returns a short hint describing how to establish one (launch_aedt or connect_to_aedt). When a session is active, it returns full status information.

This makes the tool the recommended pre-flight call to decide whether to launch_aedt (no active session) or connect_to_aedt (existing session detected).

This tool retrieves comprehensive information from the connected AEDT instance including version, active projects, designs, and connection details.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses the unusual always-reachable behavior before a connection exists, describes the degraded return (a short hint) versus the full return (version, projects, designs, connection details), and makes clear this is a non-destructive status read. It does not explicitly state read-only semantics or any side effects, which keeps it short of a 5.

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?

Purpose is front-loaded and the when-to-use guidance follows immediately, with no filler. The final paragraph restates ground already covered by "returns full status information" and is the one sentence that does not fully earn its place.

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

Completeness5/5

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

For a zero-parameter pre-flight tool with an output schema, this is complete: the agent learns the tool is always callable, what each outcome means, and which sibling to call next in each branch. Return-value detail beyond that is already handled by the output schema, so no further narrative is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate and no schema coverage gap to compensate for. Baseline 4 applies; the description correctly avoids inventing parameter behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource ("Check the status of AEDT initialization") and the rest pins down scope: reachable before any connection, returns a hint when no session, full status when one exists. This is clearly distinguishable from siblings like connect_to_aedt and launch_aedt, which the description explicitly positions it against.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly labels itself the "recommended pre-flight call" and gives the decision rule: use it to decide whether to call launch_aedt (no active session) or connect_to_aedt (existing session detected). Both alternatives and the condition selecting each are named, leaving nothing to inference.

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