Skip to main content
Glama

FEM Buckling Results

fem_buckling_results
Read-only

Extract buckling load multipliers and mode factors from a completed FEM buckling analysis by analysis name or finished job ID.

Instructions

Extract buckling load multipliers from a completed buckling run. Pass analysis, or the job_id of a finished fem_run_submit solve. Returns {buckling_factors: [...], modes: [{mode, factor}, ...]}.

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_buckling_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

A3.7/5.0
Behavior4/5

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

The annotations already declare this as a read-only, closed-world operation; the description adds useful behavior by requiring a completed/finished run and by showing the return structure. It still does not describe what happens if the run is incomplete or the job is missing/wrong type, so some operational behavior remains unstated.

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 sentences cover purpose, input selection, and return shape with no filler, and the purpose is front-loaded. Every sentence earns its place.

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 read-only result-extraction tool without an output schema, providing the return shape is important and present. However, selection semantics are thin for optional zero-required parameters: `workspace` is unexplained, mutual exclusivity of `analysis`/`job_id` is only implied, and incomplete-job behavior is not covered.

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 schema documents only `workspace`, and the description adds meaning for `job_id` (finished fem_run_submit solve) and `analysis` as an alternative. It does not explain the expected format of `analysis`/`job_id`, mutual exclusivity, or the `workspace` parameter, so it only partially compensates for the low schema description coverage.

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: extract buckling load multipliers from a completed buckling run, and names the return fields. It clearly focuses on buckling rather than modal/thermal/generic results, but it does not explicitly contrast itself with siblings such as fem_results or fem_modal_results, so it falls short of a 5.

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?

It gives the key prerequisite (a completed buckling run or finished fem_run_submit solve) and says to pass `analysis` or `job_id`, which implies when the tool applies. However, it does not explicitly name alternatives like fem_results/job_result or state when not to use this tool, leaving the routing guidance implied rather than explicit.

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