ANSYS MCP Server

Overview Schema Source Related Servers Discussions Admin

Create Geometry Block

geometry_create_block

Creates a 3D block in ANSYS geometry with specified width, height, and length, centered at given coordinates using SI units.

Instructions

Create a centered block using SI length units.

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

Input Schema

Name	Required	Default
`name`	No	Block
`width`	No
`height`	No
`length`	No
`center_x`	No
`center_y`	No
`center_z`	No

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

Behavior3/5

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

Annotations provide basic hints (readOnlyHint=false, destructiveHint=false), and the description adds useful context about the block being centered and using SI units. However, it does not disclose side effects, relationship to an existing design, or output details.

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?

The description is a single, front-loaded sentence with no waste. It is appropriately concise for expressing the core purpose, though it sacrifices detail for brevity.

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?

With 7 parameters, 0% schema descriptions, and no parameter clarifications, the description is far from complete. It does not explain how center coordinates affect placement, what the output means, or any operational context.

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% and the description provides almost no parameter-specific guidance. It mentions SI length units, which applies to dimensions, but does not explain width, height, length, center coordinates, or name, leaving the agent to guess.

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 verb 'Create' and the resource 'block', and includes a distinguishing feature ('centered', 'SI length units') that differentiates it from sibling tools like geometry_create_cylinder and geometry_create_sphere.

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 a block is needed, but provides no explicit guidance on when to prefer this over alternatives like cylinder or sphere. There are no exclusions or alternative tool references.

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