ANSYS MCP Server

Overview Schema Source Related Servers Discussions Admin

Read Mechanical Mesh Settings

mechanical_get_mesh_settings

Read-onlyIdempotent

Retrieve global mesh settings and generated counts from ANSYS Mechanical to verify configuration and monitor meshing progress.

Instructions

Read configured global mesh settings and generated counts.

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

Input Schema

Name	Required	Description	Default
No arguments

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

A4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description does not need to restate safety. It adds minimal context by mentioning 'configured global mesh settings' and 'generated counts,' but does not elaborate on what these include or any edge cases beyond the annotations.

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 filler or redundancy. It directly communicates the tool's function in a compact and scannable format, earning maximum points for conciseness.

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

Completeness4/5

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

Given the tool's simplicity (no parameters), strong annotations (read-only, idempotent), and the presence of an output schema, the description is sufficiently complete. It clearly states what is read, and the output schema likely details the return structure. A minor gap is the lack of clarity about what 'global mesh settings' includes, but this is acceptable given the output schema's role.

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?

The input schema is empty (0 parameters), so there are no parameter semantics to explain. Schema description coverage is 100% by nature, and the description accurately reflects the no-input nature. Baseline 4 applies due to 0 parameters.

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 reads configured global mesh settings and generated counts, which is a specific verb-resource combination. It distinguishes itself from sibling tools like mechanical_mesh (likely setting or creating mesh) and mechanical_get_result (getting results) by focusing on global settings and counts.

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 used to read mesh settings, but it does not explicitly state when to use it versus alternatives. There is no mention of exclusions or preferred scenarios, leaving the agent to infer usage from the verb 'Read' and context.

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