ANSYS MCP Server

by Bettertoo2

Overview Schema Source Related Servers Discussions Admin

Python

Local

Hook Fluent UDF

fluent_hook_udf

Apply custom boundary conditions by attaching a loaded UDF profile to a boundary field in Fluent.

Instructions

Attach a loaded UDF profile to a boundary field.

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": {
      "zone_name": "<zone_name>",
      "profile_name": "<profile_name>"
    },
    "name": "fluent_hook_udf"
  }
}

Input Schema

Name	Required	Default
`zone_name`	Yes
`phase_name`	No	water
`profile_name`	Yes
`momentum_field`	No	mass_flow_rate

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?

The annotations are all false (readOnlyHint, openWorldHint, idempotentHint, destructiveHint), so they provide no behavioral safety profile. The description adds no details about side effects, whether the boundary field is modified in memory or persisted, or if any validation occurs. It only states the action without any behavioral context.

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 sentence that is concise and front-loaded. It contains no filler or redundant information. Every word contributes to the action and target.

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 the tool has 4 parameters (2 required) and a moderate schema, the description is insufficient. It does not explain what 'attach' entails, what output to expect, or any preconditions. Although an output schema exists, the description still needs to convey purpose and usage context. The tool is underspecified for the complexity involved.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/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 for parameter semantics. It does not mention any parameter names, meanings, or relationships. The description adds no value beyond the input schema, leaving the agent to infer parameter semantics solely from the JSON 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 uses a specific verb ('attach') and clearly identifies the resource ('a loaded UDF profile to a boundary field'). It distinguishes this tool from siblings like fluent_load_udf (which loads UDFs) and fluent_list_udfs (which lists them). This makes the purpose unambiguous.

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 implicitly states that the UDF must already be loaded (by saying 'loaded UDF'), which provides minimal usage guidance. However, it does not explicitly mention when to use this tool over alternatives or any prerequisites beyond loading. It does not discuss context or exclusions.

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