Skip to main content
Glama

FEM Cantilever Demo

fem_cantilever_demo
Destructive

Runs a cantilever beam FEM demo end-to-end—geometry, mesh, and CalculiX solve—returning displacement, stress, and mesh data for validation.

Instructions

Run the built-in cantilever FEM demo end-to-end (geometry → mesh → CalculiX).

Dimensions in mm, force in N. Returns {nodes, tets, max_displacement_mm, max_vonmises_mpa, workdir}. A fresh document is created; existing state in the session is NOT overwritten but a new document becomes active.

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

Input Schema

NameRequiredDescriptionDefault
forceNo
widthNo
heightNo
lengthNo
workdirNo
mesh_sizeNo
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

A3.6/5.0
Behavior4/5

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

Annotations declare destructiveHint=true, and the description adds two things they do not: the units convention (mm, N) and the document side effect (a fresh document is created and becomes active, existing state preserved). This softens but does not clearly contradict destructiveHint — the active-document switch is itself a side effect an agent must know about. It does not mention runtime, solver requirements, or failure modes.

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?

Four tight sentences: pipeline and scope first, then units, then return shape, then side effects. No filler, and the most decision-relevant information is front-loaded.

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

Completeness3/5

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

For a 7-parameter, zero-required, no-output-schema tool it does cover the return keys (nodes, tets, max_displacement_mm, max_vonmises_mpa, workdir) and the document side effect. Still missing: what workdir does, expected runtime, whether CalculiX must be installed/available, and any hint that defaults exist for all parameters.

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 14% (just 'workspace'), so the description carries most of the burden. It contributes the missing units convention (dimensions in mm, force in N), which is genuinely valuable and absent from the schema, but six parameters (force, width, height, length, workdir, mesh_size) are left without meaning, units per-field, or valid ranges — workdir in particular is unexplained.

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 ('Run the built-in cantilever FEM demo end-to-end') and enumerates the pipeline stages (geometry → mesh → CalculiX), which implicitly separates it from the step-by-step fem_new_analysis / fem_mesh / fem_run workflow. It never names those siblings, so the differentiation 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?

The word 'demo' implies a smoke-test/quickstart use, but the description gives no explicit when-to-use, when-not-to-use, or 'use X instead for a real study' guidance despite ~15 FEM siblings. The agent has to infer that this is not the path for a custom analysis.

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