Skip to main content
Glama

FEM Modal

fem_modal
Destructive

Configure a frequency-analysis setup by setting eigenmode count and optional frequency bounds before running the solver and reading modal results.

Instructions

Configure analysis for modal (frequency) extraction.

Sets solver AnalysisType='frequency' and EigenmodesCount=n_modes. f_low / f_high (Hz) optionally bound the requested mode range. Caller still calls fem_run, then fem_modal_results to read frequencies.

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

Input Schema

NameRequiredDescriptionDefault
f_lowNo
f_highNo
n_modesNo
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. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, yet the description never says what is overwritten or invalidated — an agent cannot tell whether existing solver settings or prior results are clobbered. It does add useful beyond-annotation context: the exact property assignments and the fact that no results are produced by this call.

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?

Three short lines, front-loaded with purpose, then behavior, then the follow-up calls. No filler or restated title; every sentence carries information the agent needs.

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, and the description correctly notes that results come from a separate tool, so nothing is missing about return values. The remaining gap is the implied prerequisite (creating/selecting an analysis, e.g. via fem_new_analysis) and the destructive-overwrite semantics.

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% (only 'workspace' is documented), so the description has to compensate. It maps n_modes to EigenmodesCount and gives units and meaning for f_low/f_high (Hz, optional mode-range bounds), but leaves the required 'analysis' parameter — presumably the analysis handle/name — entirely unexplained.

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 ('Configure analysis for modal (frequency) extraction') and immediately names the concrete effects (AnalysisType='frequency', EigenmodesCount=n_modes). It also distinguishes itself from the sibling result/runner tools by explaining that it only configures and that fem_run / fem_modal_results do the rest.

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?

Explicitly lays out the call order ('Caller still calls fem_run, then fem_modal_results to read frequencies'), which tells the agent this is a setup step, not a solve or read step. It stops short of stating prerequisites (an existing analysis object) or when to pick this over fem_buckling / fem_set_solver.

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