Skip to main content
Glama

FEM Buckling

fem_buckling
Destructive

Configure linear buckling analysis by applying a unit-magnitude force at the load location; returned factors show the multipliers at which buckling occurs.

Instructions

Configure analysis for linear buckling. Apply a unit-magnitude force constraint at the load location; the result factors are the multipliers at which buckling occurs.

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

Input Schema

NameRequiredDescriptionDefault
analysisYes
n_factorsNo
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

B3.1/5.0
Behavior3/5

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

Annotations already flag destructiveHint=true and readOnlyHint=false; the description adds real context by explaining the unit-load convention and what the factors mean. It does not disclose what configuration state is overwritten, whether a solve is triggered (the word 'configure' hints no, but it is never stated), or that results are retrieved elsewhere.

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?

Two short sentences, front-loaded with the action and followed by the modeling prerequisite; no filler. The awkward line break inside the second sentence is cosmetic only.

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

Completeness2/5

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

For a destructive setup tool in a multi-step FEM workflow with no output schema and thin parameter documentation, the description omits the essential pipeline context: which analysis object it attaches to, that it does not run the solve, and that fem_buckling_results is the counterpart. An agent could call it with a wrong or missing analysis reference.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 33% and the description never names a parameter. It alludes to the meaning of n_factors ('the result factors are the multipliers...') but leaves 'analysis' (the sole required argument and the identifier for the whole operation) and its expected origin entirely undefined.

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: 'Configure analysis for linear buckling', which is clearly a setup step rather than a solve or a results read. It does not, however, distinguish itself from nearby siblings such as fem_modal, beam_buckling, or fem_buckling_results, so the agent must infer the boundary.

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?

The second sentence gives genuine modeling guidance (apply a unit-magnitude force so factors are multipliers), which is implied usage guidance for the physics setup. But there is no explicit when-to-use/when-not-to-use statement, no mention that an existing analysis from fem_new_analysis is a prerequisite, and no pointer to fem_buckling_results for reading output.

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