Skip to main content
Glama

FEM Set Nonlinear Material

fem_set_nonlinear_material

Attach an elastoplastic hardening curve to a linear FEM material and enable material nonlinearity for CalculiX solves, with yield points, hardening type, and optional large deflection.

Instructions

Attach an elastoplastic (*PLASTIC) hardening curve to a linear FEM material and switch the CalculiX solve to nonlinear — the material-nonlinearity half of the nonlinear FEM path (contact_setup is the geometric/contact half). No new solver: this promotes the CCX MaterialNonlinearity / GeometricalNonlinearity flags the FEM path already exposes. base_material is the handle from fem_set_material (its YoungsModulus/PoissonRatio stay the elastic branch).

Give the post-yield curve either as yield_points ([[stress_MPa, plastic_strain], ...], first point at plastic_strain 0 = initial yield) or from yield_mpa (+ optional tangent_modulus_mpa linear-hardening slope and max_plastic_strain). With no tangent modulus the curve is elastic–perfectly-plastic and caps the stress at σ_y exactly. hardening: 'isotropic' (monotonic) or 'kinematic' (cyclic/Bauschinger). Set geometric_nonlinearity=true to combine plasticity with large deflection (*NLGEOM). ramp_increments sub-divides the load step so ccx's plastic return-mapping converges. Run fem_run + fem_results after; gate against plastic_collapse (perfectly-plastic stress saturates at σ_y, collapse at M_p).

Returns {handle, name, hardening, yield_points, n_points, solver_material_nonlinear, solver_geometric_nonlinear, ramp_increments}.

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": {
      "analysis": "<analysis>",
      "base_material": "<base_material>"
    },
    "name": "fem_set_nonlinear_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNonlinearMaterial
analysisYes
hardeningNoisotropic
workspaceNoRun this call in this named workspace
yield_mpaNo
yield_pointsNo
base_materialYes
ramp_incrementsNo
max_plastic_strainNo
tangent_modulus_mpaNo
geometric_nonlinearityNo

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.8/5.0
Behavior5/5

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

Annotations declare non-read-only, non-destructive, closed-world; the description goes well beyond that by explaining the state change semantics ('no new solver: promotes the CCX MaterialNonlinearity / GeometricalNonlinearity flags'), that the base material's E/nu remain the elastic branch, and physical consequences ('no tangent modulus → elastic–perfectly-plastic and caps the stress at σ_y'). It also discloses the convergence lever (ramp_increments subdivides the load step so plastic return-mapping converges) — the exact kind of operational caveat annotations cannot express.

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?

Front-loaded with purpose and discrimination, then parameter semantics, then return/workflow — a clean progression with zero filler sentences and parameters marked in backticks. It is dense and long (~230 words) with heavy parenthetical tangents (e.g. the M_p collapse aside), which costs it the top score but every sentence does carry information at 9% schema coverage.

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 an 11-parameter mutation tool with no output schema, it still names the returned fields ({handle, name, hardening, yield_points, n_points, solver_material_nonlinear, solver_geometric_nonlinear, ramp_increments}) and describes the full downstream workflow. Nothing an agent needs in order to call it and interpret the result is missing.

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?

Schema description coverage is only 9% for 11 parameters, so the description must carry the load, and it largely does: it defines base_material's provenance, yield_points' [[stress_MPa, plastic_strain], ...] layout with the 'first point at plastic_strain 0 = initial yield' rule, hardening's 'isotropic'/'kinematic' meaning, tangent_modulus_mpa, max_plastic_strain, geometric_nonlinearity, and ramp_increments. The gaps are 'analysis' and 'name', which are never explained (workspace gets only a schema description).

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?

Opens with a specific verb+resource ('Attach an elastoplastic (*PLASTIC) hardening curve to a linear FEM material and switch the CalculiX solve to nonlinear') and explicitly positions itself against its sibling contact_setup as 'the material-nonlinearity half of the nonlinear FEM path'. An agent can distinguish it from fem_set_material, contact_setup, and fem_run 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 Guidelines5/5

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

Gives explicit prerequisites (base_material 'is the handle from fem_set_material'), the ordering constraint ('Run fem_run + fem_results after'), which sibling to use for the other half (contact_setup), and a concrete verification target ('gate against plastic_collapse'). It also states the alternative input forms (yield_points vs yield_mpa+tangent_modulus_mpa) with the condition selecting each.

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