ANSYS MCP Server

Overview Schema Source Related Servers Discussions Admin

Apply Mechanical Load

mechanical_apply_load

Apply a force, pressure, fixed support, or displacement to a uniquely named selection in ANSYS Mechanical with optional magnitude, direction, and units.

Instructions

Apply one typed load or support to one uniquely named selection.

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": {
      "load_type": "<load_type>",
      "location": "<location>"
    },
    "name": "mechanical_apply_load"
  }
}

Input Schema

Name	Required	Description	Default
`location`	Yes
`direction`	No
`load_type`	Yes
`magnitude`	No
`analysis_index`	No
`magnitude_unit`	No

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

B3.3/5.0

Behavior2/5

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

With annotations indicating the tool is not read-only and not idempotent, the description adds no additional behavioral detail about mutation semantics, whether loads accumulate or overwrite, or side effects. The one-line description does not disclose these essential traits beyond what annotations already provide.

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?

The description is a single, front-loaded sentence with no wasted words. It immediately states the action and target, making it concise and well-structured despite the underlying complexity.

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?

Despite having an output schema, the description omits prerequisites, parameter semantics, and how this tool fits into the Mechanical workflow relative to siblings like mechanical_mesh or mechanical_solve. For a 6-parameter tool, the description is far too thin to be contextually complete.

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 description coverage is 0%, and the description only hints at 'load or support' mapping to load_type and 'named selection' mapping to location. It leaves direction, magnitude, magnitude_unit, and analysis_index completely unexplained, providing only marginal value over the raw schema.

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 'Apply one typed load or support to one uniquely named selection' uses a specific verb and resource, clearly indicating it applies loads/supports to named selections. It distinguishes itself from sibling tools like mechanical_mesh and mechanical_solve in the Mechanical workflow.

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?

The description implies the tool is for applying loads/supports to named selections, which gives clear context, but it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites.

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