Skip to main content
Glama

FEM Run Submit

fem_run_submit
Destructive

Submits a long-running CalculiX FEM analysis as a background job, then poll job status until completion imports results into the analysis.

Instructions

Run the CalculiX solver on an analysis OFF the MCP channel — the submit→poll form of fem_run, for solves long enough to stall the channel (see fem_run for which to use).

The solver input is written before this returns, so a missing solver, material or mesh fails here, synchronously, exactly as fem_run would. ccx then runs in the background. Poll job_status: once ccx exits, the results are imported into the analysis on your NEXT poll (FreeCAD work runs on the worker's main thread, which a poll gives a turn) — so keep polling until status is 'done'; a job nobody polls never finishes. A ccx error fails the job with its *ERROR lines.

When done, read results with fem_results / fem_result_probe / fem_modal_results / fem_buckling_results / fem_thermal_results passing either analysis or this job_id (don't job_result(discard=True) first if you plan to use the job_id). While the job runs, fem_run or another submit on the same analysis or workdir is refused. Returns {job_id, status, cache_hit}; job_result's result is fem_run's return dict.

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_run_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
workdirNo
analysisYes
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. Addedv0.5.5

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare destructive write behavior, and the description goes far beyond them: synchronous pre-flight validation of solver/material/mesh, background ccx execution, the mandatory polling requirement ('a job nobody polls never finishes'), deferred result import on the next poll, *ERROR failure semantics, and a caution against job_result(discard=True) if the job_id will be reused.

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 the key distinction, then the lifecycle. It is dense and slightly meandering with stacked parentheticals, but nearly every sentence carries operational value (validation timing, polling rule, error behavior, return shape).

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?

No output schema exists, and the description compensates by describing the return dict {job_id, status, cache_hit} and how job_result relates to it. The full submit→poll→read-results workflow is covered, leaving no ambiguity about what to do after the call.

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 coverage is only 33% (only `workspace` is described), so the description carries extra load. It implies `workdir` is the solver working directory that also acts as a job lock ('refused on the same analysis or workdir') and clarifies `analysis` as the target; it also names the return keys, but doesn't spell out workdir's default/format behavior.

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?

States a specific verb+resource (CalculiX solver on an analysis) and immediately names its form and sibling relationship: 'the submit→poll form of fem_run'. An agent can distinguish it from fem_run without opening either 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 an explicit selection criterion ('solves long enough to stall the channel') and points to the alternative ('see fem_run for which to use'). Names the refusal condition (fem_run or another submit on the same analysis/workdir) as well.

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