ANSYS MCP Server

Overview Schema Source Related Servers Discussions Admin

Execute Mechanical Script

mechanical_script

Destructive

Execute custom IronPython scripts in ANSYS Mechanical to automate simulations, modify models, or extract data. Requires explicit confirmation for unsafe operations.

Instructions

Execute arbitrary Mechanical IronPython after explicit unsafe confirmation.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "script": "<script>",
      "confirm_unsafe": "<confirm_unsafe>"
    },
    "name": "mechanical_script"
  }
}

Input Schema

Name	Required	Description
`script`	Yes
`timeout`	No
`confirm_unsafe`	Yes	Explicit confirmation that arbitrary IronPython can modify Mechanical

Output Schema

Name	Required	Description	Default
`ok`	Yes
`data`	No
`tool`	Yes
`error`	No
`message`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Aug 14, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, and the description adds 'unsafe confirmation,' reinforcing the risk. It does not detail side effects or that arbitrary code can modify Mechanical state (though the schema does for confirm_unsafe). Given annotation coverage, the description adds minimal extra context, so a 3 is appropriate.

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?

One short sentence, front-loads the verb and resource, with no filler. Perfectly concise.

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

Completeness2/5

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

This is a powerful tool with arbitrary code execution and a destructive hint, yet the description provides only one sentence. It does not describe return behavior, error conditions, or what state changes may occur. With an output schema present but not described, and significant execution risk, the description is insufficient for full understanding.

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

Parameters2/5

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

Schema coverage is only 33% (only confirm_unsafe has a description). The description mentions 'arbitrary Mechanical IronPython' and 'unsafe confirmation,' which loosely map to script and confirm_unsafe, but it never mentions the timeout parameter, leaving its semantics unclear. The description does not compensate for the schema's lack of descriptions.

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 description specifies a clear verb ('Execute') and resource ('Mechanical IronPython'), and the qualifier 'after explicit unsafe confirmation' distinguishes it from other Mechanical operations. It clearly separates from sibling tools that perform specific actions like solve or get_result.

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

Usage Guidelines4/5

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

The word 'arbitrary' implies use for custom operations not covered by specific sibling tools, and the unsafe confirmation indicates it's for advanced users. However, it doesn't explicitly state when to prefer this over other tools or provide exclusions, so it's clear context but lacks explicit guidance.

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