Mechanical MCP Server

by codersag

Overview Schema Source Related Servers Discussions Admin

Python

Local

add_reaction_force

Creates a force reaction probe at a named selection in an ANSYS Mechanical analysis to measure reaction forces.

Instructions

Add Force Reaction probe at a named selection. Args: named_selection, analysis_index

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": {
      "named_selection": "<named_selection>"
    },
    "name": "add_reaction_force"
  }
}

Input Schema

Name	Required	Description	Default
`analysis_index`	No
`named_selection`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Oct 17, 2026

TDQS

C2.7/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 behavioral burden, yet it discloses almost nothing: no precondition that a Mechanical connection and an existing named selection are required, no statement about which analysis the probe attaches to, and no indication of side effects. It only names the created object.

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?

Two short sentences, front-loaded with the core action. The 'Args:' fragment adds little beyond the schema, but the description is not bloated.

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?

An output schema exists, so return values need no explanation, but the definition omits the prerequisites and parameter meaning an agent needs to invoke it correctly. Given the sibling set implies a live Mechanical session, the missing connection/named-selection context is a real gap.

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%, so the description must compensate, but 'Args: named_selection, analysis_index' merely restates the parameter names. It never explains what analysis_index means (default 0) or that named_selection must reference an existing selection created via list_named_selections.

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: 'Add Force Reaction probe at a named selection.' This clearly distinguishes it from siblings that add stress, deformation, or boundary-condition objects. It stops short of explicitly contrasting with the closest alternatives, but the resource is unambiguous.

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 context, no prerequisites, and no mention of alternatives such as add_principal_stress or add_equivalent_stress. The agent must infer that this is an analysis-setup probe tool from the name alone.

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