Skip to main content
Glama

FEM Set Material

fem_set_material

Assign a material to a body in a FEM analysis so simulation uses its Young's modulus, Poisson ratio, density, and other material card properties.

Instructions

Bind a material to a body in an analysis.

material is a dict with at minimum: {"YoungsModulus": "210000 MPa", "PoissonRatio": "0.30", "Density": "7900 kg/m^3", "Name": "Steel-Generic"} Any extra keys are passed through to the FEM material card.

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>",
      "body": "<body>",
      "material": "<material>"
    },
    "name": "fem_set_material"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
nameNoMaterial
analysisYes
materialYes
workspaceNoRun this call in this named workspace

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

B3.3/5.0
Behavior3/5

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

Annotations already state readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds useful behavior by explaining that extra material keys are passed through to the FEM material card, but it does not say whether an existing material binding is overwritten or what prerequisites apply.

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 front-loaded with the operation, then provides a compact material example and pass-through note. Every part earns its place, especially the material schema example, which fills a significant gap in the structured schema.

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

Completeness3/5

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

For a five-parameter mutation with no output schema, the description covers the key nested material object and annotations cover the safety profile. It still omits prerequisites, overwrite semantics, and the meaning of analysis/body/name, leaving it only minimally complete.

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

Parameters3/5

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

Schema coverage is only 20%, and the material parameter is otherwise an opaque object with additionalProperties=true. The description compensates well for that nested object by giving minimum keys, example units, and a pass-through rule, but analysis, body, and name remain undocumented beyond bare titles/defaults.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb ('Bind') and names the resources involved: material, body, and analysis. The operation is immediately identifiable, but it does not explicitly distinguish itself from sibling tools such as fem_set_nonlinear_material or material_select.

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

Usage Guidelines2/5

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

The description gives no explicit when-to-use or when-not-to-use guidance and does not name alternatives. The phrase 'in an analysis' supplies context but not selection criteria, so an agent must infer when this tool is appropriate versus other FEM/material tools.

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