Skip to main content
Glama

FEM Modal Results

fem_modal_results
Read-only

Extract natural frequencies and mode details from a completed modal analysis or finished FEM solve by passing an analysis name or job_id.

Instructions

Extract natural frequencies from a completed modal run. Pass analysis, or the job_id of a finished fem_run_submit solve. Returns {frequencies_hz: [...], modes: [{mode, frequency_hz, max_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_modal_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4.2/5.0
Behavior4/5

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

The annotations already establish a safe read-only operation, and the description adds useful context: this only applies to completed modal runs and returns frequencies plus per-mode displacement data. It does not cover error behavior when the run is incomplete or how multiple selectors are resolved.

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 purpose, then immediately states accepted selectors and return shape. Every sentence contributes directly to invoking or interpreting the tool.

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?

For a simple result-extraction tool, it is close to complete: it gives the return structure even without an output schema and ties invocation to a completed solve. The remaining gap is selector semantics for `analysis` versus `job_id`.

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?

The description clarifies that `job_id` refers to a finished `fem_run_submit` solve and that `analysis` is an alternative selector. However, with low schema coverage, it still leaves ambiguity about what `analysis` should contain and whether `analysis` and `job_id` are mutually exclusive or prioritised.

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?

The description states a specific verb and resource: extracting natural frequencies from a completed modal run. It also frames the operation around a finished fem_run_submit solve, which helps distinguish it from setup or generic result tools.

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

Usage Guidelines4/5

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

It clearly says the run must be completed and that either `analysis` or a finished solve's `job_id` should be passed. It does not explicitly contrast this with siblings such as `fem_results` or `fem_result_probe`, so it is strong but not exhaustive.

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