ANSYS MCP Server

Overview Schema Source Related Servers Discussions Admin

Configure Mechanical Mesh

mechanical_mesh

Configure mesh element size and method for ANSYS Mechanical, with optional mesh generation. Select from automatic, tetrahedrons, or hex-dominant for desired mesh quality.

Instructions

Configure mesh size and method, then optionally generate the mesh.

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

Input Schema

Name	Required	Default
`method`	No	automatic
`timeout`	No
`generate`	No
`element_size`	No
`element_size_unit`	No	mm

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.1/5.0

Behavior2/5

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

Annotations provide no hints (all false), so the description carries the burden. It mentions 'optionally generate' but does not disclose side effects of changing mesh settings, whether generation is blocking, what the timeout parameter controls, or if prior model setup is required. This is insufficient for a mutating tool.

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 that efficiently conveys the core action and optional outcome. It wastes no words and is appropriately sized for the tool's 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?

Given 5 parameters and no annotation support, the description is too sparse. It does not explain the generate flag's effect, timeout semantics, element size unit implications, or how this step fits into the broader meshing/solving workflow, even though an output schema exists.

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. It mentions 'mesh size' and 'method', which maps to element_size and method, but ignores element_size_unit, generate, and timeout. The schema only provides titles/enums, leaving these parameters under-explained.

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 clearly states the tool configures mesh size and method and optionally generates the mesh, using a specific verb and resource. It distinguishes from sibling tools like mechanical_get_mesh_settings (which reads settings) and mechanical_apply_load (which applies loads), so the purpose 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?

The description gives no explicit guidance on when to use this tool versus alternatives, such as mechanical_get_mesh_settings for reading current mesh settings. It implies use before solving but does not state prerequisites, exclusions, or alternative scenarios.

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