Skip to main content
Glama

FEM Results

fem_results
Read-only

Extract maximum von Mises stress, displacement, and top stress nodes from a completed finite element analysis or solve job ID.

Instructions

Extract summary results from an analysis.

Pass analysis, or the job_id of a finished fem_run_submit solve (a running or failed job is an error that says so).

Returns {max_vonmises_mpa, max_displacement_mm, max_displacement_vector, top_stress_nodes: [{node, vonmises_mpa, displacement_mm}, ...]}.

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

Input Schema

NameRequiredDescriptionDefault
top_nNo
job_idNo
analysisNo
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. Changed5 schema fields changedv0.5.5
    • addedInput schema / properties / analysis / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / analysis / default
      Added value: +null
    • removedInput schema / properties / analysis / type
      Removed value: -"string"
    • addedInput schema / properties / job_id
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Job Id"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "analysis"
      -]
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context beyond that: the error condition for running/failed jobs and the exact return payload. It stops short of noting cost, pagination, or whether results are cached/recomputed.

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?

Front-loaded verb phrase, then the input rule, then the return shape — three tight statements with no filler. Given there is no output schema, the return signature is not 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?

With no output schema, including the return shape is exactly the right compensation, and the job-state error is disclosed. Missing pieces are minor but real: the meaning/default of `top_n` and the accepted form of `analysis` (name vs handle vs document).

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 25% (just `workspace`), so the description must compensate. It does explain that `analysis` and `job_id` are alternative selectors, which is the key ambiguity. But `top_n` is never described (its link to top_stress_nodes length is only inferable) and the `analysis` argument format 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?

Specific verb+resource: 'Extract summary results from an analysis'. It implies a static structural summary versus the modal/thermal/buckling result siblings, but never names those alternatives explicitly, so the distinction is inferred rather than stated.

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?

It gives a clear input-selection rule (pass `analysis` OR the `job_id` of a finished fem_run_submit solve) and flags that running/failed jobs error out. It does not say when to use this instead of fem_result_probe, render_fem_results, or the per-physics result tools, so guidance is implied rather than comparative.

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