Skip to main content
Glama
gchen19

AnkusDrive

by gchen19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

FEM Buckling Results

fem_buckling_results
Read-only

Extract buckling load multipliers and mode shapes from a completed buckling simulation by passing the job ID or analysis reference.

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}, ...]}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idNo
analysisNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
-]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description reinforces this by saying it 'extracts' results without suggesting any mutation. It also adds useful behavioral context by specifying the prerequisite of a completed run and by showing the exact return shape, which the agent would otherwise not know without an output schema.

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 three short sentences with no filler. It front-loads the core purpose, then provides invocation guidance, then the return format. Every sentence earns its place and the structure is easy to scan.

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?

For a read-only result extraction tool with optional parameters and no output schema, the description covers the key elements: what it extracts, how to invoke it, when it is valid, and what it returns. It could be slightly more explicit about whether passing both `analysis` and `job_id` is allowed or how conflicts are resolved, but this is a minor gap.

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 0%, so the description must compensate for the bare parameter names. It does so by explaining that `analysis` and `job_id` are alternative identifiers and that `job_id` refers to a finished `fem_run_submit` solve, giving the agent enough semantic grounding for both parameters.

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?

The description uses a specific verb ('Extract') and a specific resource ('buckling load multipliers from a completed buckling run'), making the tool's purpose immediately clear. It also distinguishes itself from related FEM tools by focusing specifically on buckling result extraction rather than setup, submission, or generic result retrieval.

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?

The description clearly states the precondition: the buckling run must be completed, and it tells the agent to pass either `analysis` or the `job_id` of a finished `fem_run_submit` solve. It does not explicitly name alternative result tools like `fem_modal_results` or `fem_thermal_results`, but the context strongly implies when this tool is appropriate.

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