ANSYS MCP Server

by Bettertoo2

Overview Schema Source Related Servers Discussions Admin

Python

Local

Read Fluent Residuals

fluent_get_residuals

Read-onlyIdempotent

Retrieve current Fluent residual values from ANSYS simulation to assess convergence.

Instructions

Read the latest Fluent residual values.

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

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

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds the 'latest' qualifier, providing temporal context, but does not disclose behavior like empty results when no residuals exist. This is a minor addition beyond 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 unnecessary words. It conveys the exact purpose efficiently.

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

Completeness5/5

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

For a parameterless tool with clear read-only annotations and an output schema, this one-sentence description is sufficiently complete. It specifies what is returned (residuals) and their recency (latest), with no critical missing context.

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 tool has zero parameters, and the schema is empty with 100% coverage, so the description carries no burden for parameter meaning. The baseline of 4 applies as no parameter information is needed.

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 uses the specific verb 'Read' and identifies the resource as 'the latest Fluent residual values,' making its function unmistakable. It distinguishes itself from sibling tools like fluent_status or fluent_get_mapping_report by focusing on residuals.

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 usage (when you need residual values) but provides no explicit context, alternatives, or exclusions. There is no mention of when to use this over other fluent read tools.

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