Skip to main content
Glama

Topology Optimize Submit

topology_optimize_submit

Submit an asynchronous SIMP topology optimization for 2D or 3D domains to find the stiffest layout under a density constraint; poll the job for resulting density geometry.

Instructions

Minimum-compliance topology optimization (in-house SIMP; NO external solver), asynchronous because each iteration solves an FE system. Optimizes a 2-D rectangular design domain (nelx×nely unit cells) — or, when nelz is set, a 3-D nelx×nely×nelz grid of trilinear hexahedra — to the stiffest layout that holds Σdensity = keep_fraction (the Optimality-Criteria update holds it exactly); penal is the SIMP penalty (≈3), rmin the cone filter radius. Default BCs (both): the whole left face clamped + a unit downward load at the right-face centre. 2-D overrides: fixed_dofs / load=[dof_index, value]. 3-D overrides: loads=[[i,j,k,axis,value],...] point loads at node grid coords (axis 'x'|'y'|'z'), fixed_nodes=[[i,j,k],...] clamped nodes, and keep_out/keep_in lists of half-open element-index boxes [i0,i1,j0,j1,k0,k1] forced void / forced solid (keep-out regions and must-keep pads).

Returns immediately {job_id, status, cache_hit}; poll job_result for {density (2-D: nely×nelx grid; 3-D: nelz×nely×nelx voxel field, density[k][j][i] with j=0 at the bottom — this IS geometry), mass_fraction (==keep_fraction), compliance, compliance_initial, iterations, converged, gray_fraction, solver (3-D: which linear-solve backend ran)}. Threshold + voxel→solid back in the modeller with topology_to_solid, then gate with mass_properties (mass ≤ keep_fraction·original) and interference_check vs keep-outs.

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

Input Schema

NameRequiredDescriptionDefault
tolNo
loadNo
nelxNo
nelyNo
nelzNo
rminNo
loadsNo
penalNo
keep_inNo
keep_outNo
max_iterNo
workspaceNoRun this call in this named workspace
fixed_dofsNo
fixed_nodesNo
keep_fractionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the asynchronous submit-and-poll contract, the in-house SIMP solver, the Optimality-Criteria update holding Σdensity exactly at keep_fraction, and the default boundary conditions used when no overrides are given. It also flags the non-obvious result semantics ('density[k][j][i] with j=0 at the bottom — this IS geometry'), which is exactly the kind of context annotations cannot carry.

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?

Purpose and asynchrony are front-loaded, and virtually every clause carries information that would otherwise be missing from the sparse schema. It is dense with backticked notation and long parenthetical clauses, though, which makes it harder to scan than a bulleted layout would be.

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?

There is no output schema, so the description carries the return contract itself and does so fully: immediate {job_id, status, cache_hit} plus the full job_result field list with shape and orientation conventions for both 2-D and 3-D. Combined with the workflow hand-off to topology_to_solid, an agent has everything needed to call and consume this tool.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 7%, so the description must compensate, and it does: nelx/nely/nelz, keep_fraction, penal, rmin, fixed_dofs, load, loads, fixed_nodes, keep_out and keep_in are all given meaning, including the dof_index/value and [i,j,k,axis,value] tuple formats and the half-open box convention. Only tol and max_iter are left undocumented, a minor residue against 15 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?

Names a specific verb+resource (minimum-compliance topology optimization, in-house SIMP) and immediately differentiates itself from solver-backed siblings with 'NO external solver'. It also states the exact design-domain shape and objective, so an agent knows precisely what this produces without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent this is asynchronous and to 'poll job_result', and lays out the downstream chain (topology_to_solid → mass_properties → interference_check vs keep-outs), naming the sibling tools. It does not state when to prefer a different optimization tool (e.g. optimize_submit) or when not to use this one, so it stops short of full routing guidance.

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

Deploy Server

Other Tools