Skip to main content
Glama
PyAEDT-MCP
by yuxuan6426

Check Aedt Installed

check_aedt_installed

Checks for valid AEDT installations and returns available versions; in Docker, probes the configured remote gRPC endpoint instead of a local install.

Instructions

Check if AEDT is installed on the system.

This tool checks for valid AEDT installations on the system and returns information about available versions.

When running inside a Docker container, the tool probes the remote gRPC endpoint (AEDT_MACHINE:AEDT_PORT) instead of searching for a local AEDT installation.

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_installed"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 burden, and it does disclose one genuinely useful behavior: in Docker it probes a remote gRPC endpoint (AEDT_MACHINE:AEDT_PORT) rather than scanning locally. However, it never states that the tool is read-only/non-destructive, what happens on failure or timeout, or whether probing a remote endpoint requires a reachable server.

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?

Front-loaded with the core purpose in one sentence, followed by supporting detail about versions and the Docker caveat. The middle sentence slightly restates the opening ('checks for valid AEDT installations'), but overall it is tight for the information conveyed.

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?

An output schema exists, so return values need not be described. For a zero-parameter, non-destructive probe, the definition covers purpose, version reporting, and the container/remote-endpoint edge case — enough for an agent to call it correctly.

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?

Zero parameters, so there is no parameter semantics to document; the schema is empty and fully closed. Baseline of 4 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?

States a specific verb and resource ('Check if AEDT is installed') and adds useful scope: it reports available versions, not just a boolean. It does not explicitly differentiate itself from nearby siblings such as check_aedt_status, launch_aedt, or connect_to_aedt, so an agent must infer the boundary between 'installed' and 'status' checks.

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 Docker note hints this is a pre-flight probe run before connecting or launching, but there is no explicit 'use this before X' or 'do not use this for Y' statement. No exclusions are given relative to check_aedt_status or connect_to_aedt.

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