Skip to main content
Glama

FEM Set Solver

fem_set_solver

Adds a CalculiX or Elmer solver to a FEM analysis and sets solver properties, filling CalculiX defaults when omitted.

Instructions

Add a solver to an analysis. kind: 'ccx' (CalculiX) or 'elmer'.

tunables: dict of solver-property values, e.g. {"GeometricalNonlinearity": "linear", "ThermoMechSteadyState": True, "MatrixSolverType": "default"}. Sensible CCX defaults are filled in if omitted.

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>"
    },
    "name": "fem_set_solver"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoccx
nameNoSolver
analysisYes
tunablesNo
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

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, openWorld=false, so the safety profile is covered. The description adds genuinely useful behavior – that omitted tunables get sensible CCX defaults – but says nothing about whether an existing solver is replaced, whether deletion is possible, or what happens on invalid tunables. For a mutation tool, this is an adequate but incomplete disclosure.

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 core action is front-loaded in the first sentence, followed by the kind values and a concrete tunables example. Somewhat tersely formatted with fragmented lines, but every sentence adds information and nothing is padding.

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

Completeness4/5

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

No output schema exists, so the description bears the role of explaining configuration semantics, and the tunables example goes a long way toward making the call actionable. Gaps remain around the required 'analysis' reference form and order-of-operations within the FEM workflow, but the essential setup guidance is present.

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% (just the workspace field), so the description needs to compensate. It does explain 'kind' (ccx/elmer) and gives a concrete tunables example plus the default-fill behavior, but leaves 'name' and the required 'analysis' parameter semantically unaddressed, and typo/valid-key behavior for tunables is unspecified.

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?

States a specific verb and resource: 'Add a solver to an analysis'. Combined with the kind enum values ('ccx' or 'elmer'), an agent understands this configures a solver object. It does not explicitly name how it differs from sibling setup steps like fem_set_material or fem_add_constraint, but the domain is clear.

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?

Implies it belongs to the FEM analysis-setup sequence and notes that CCX defaults are auto-filled, which is useful context. However it never states preconditions (e.g., analysis must already exist, materials may need setting first) or when to choose elmer over ccx beyond listing the values.

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