Skip to main content
Glama

FERS — structural FEM

Add a geometric imperfection

add_imperfection_case
Read-only

Add a geometric imperfection — a global sway (out-of-plumb lean, EN 1993-1-1 §5.3.2) and/or a member bow — bound to specific load combinations. The solver perturbs the geometry before solving those combinations, so it feeds both first-order and P-Delta results. Give the sway as a ratio denominator (200 means a 1/200 lean); it is stored in radians. IMPORTANT: the engine ignores an unknown combination id SILENTLY, so a typo would apply no imperfection at all — this tool rejects unknown ids instead. Free.

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": {
      "load_combination_ids": "<load_combination_ids>"
    },
    "name": "add_imperfection_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoStringified FERS model JSON
model_refNoHandle from stash_model, used INSTEAD of `model`. Avoids sending the whole document on every step; the tool returns the same handle back.
sway_axis_xNoSway rotation axis X (default 0).
sway_axis_yNoSway rotation axis Y (default 0).
sway_axis_zNoSway rotation axis Z (default 1). The lean direction is axis x height_direction.
height_direction_xNoDirection height is measured along, X (default 0).
height_direction_yNoY (default 1 — these models are Y-up).
height_direction_zNoZ (default 0).
sway_magnitude_radNoSway angle directly in radians, if you would rather not use a ratio (0.005 = 1/200).
translation_axis_xNoBow direction X (default 1).
translation_axis_yNoBow direction Y (default 0).
translation_axis_zNoBow direction Z (default 0).
load_combination_idsYesJSON array of combination ids this imperfection applies to, e.g. [1,2]. Required — an imperfection only affects the combinations it names.
translation_magnitudeNoBow amplitude in model length units. Required when translation_memberset_ids is given.
sway_ratio_denominatorNoSway as 1/N: pass 200 for a 1/200 lean. Converted to radians for you.
translation_memberset_idsNoJSON array of member-set ids to give a bow imperfection, e.g. [1].

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior1/5

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

The description plainly describes an add/mutation operation ('Add a geometric imperfection', solver 'perturbs the geometry'), while the annotations declare readOnlyHint=true. This is a direct contradiction, so behavioral transparency cannot be credited despite otherwise useful details about solver behavior and unknown-id handling.

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 purpose, then explains solver behavior, gives an important warning, and ends with cost. For a 16-parameter tool it is compact, and each sentence carries actionable information.

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?

Given the 16-parameter schema and no output schema, the description supplies the essential purpose, key parameter semantics, and a strong warning about silent unknown-id handling. It does not cover every parameter or removal behavior, but it is largely complete for correct invocation.

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 description coverage is 100%, so the baseline is 3. The description adds useful meaning beyond the schema for key parameters: sway can be given as a ratio denominator, is stored in radians, and load_combination_ids determines which combinations are affected.

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?

The description states a specific verb and resource: add a geometric imperfection, with global sway and/or member bow bound to load combinations. It is clear what the tool does, but it does not explicitly distinguish itself from sibling add_* tools.

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?

Usage is implied by the purpose and by the named load-combination binding, but the description gives no explicit when-to-use/when-not guidance and does not name alternatives among the sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.