Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Euler and Johnson column buckling

structural-calcs_column-buckling
Read-onlyIdempotent

Elastic Euler and inelastic Johnson-parabola critical stress/load for a pin-ended equivalent column with caller K. Price $0.02 USDC. POST /api/v1/structural-calcs/column-buckling. An unpaid call returns the x402 payment terms and does not run.

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": {
      "E": "<E>",
      "fy": "<fy>",
      "A": "<A>",
      "I": "<I>",
      "length": "<length>",
      "K": "<K>"
    },
    "name": "structural-calcs_column-buckling"
  }
}

Input Schema

NameRequiredDescriptionDefault
AYesE, number. Required.
EYesE, number. Required.
IYesE, number. Required.
KYesK, number, from 0.5 to 10. Required.
fyYesE, number. Required.
lengthYesE, number. Required.

Output Schema

NameRequiredDescriptionDefault
rNor. Number.
regimeNoregime. String.
sourcesNosources. Array.
eulerLoadNoeulerLoad. Number.
eulerStressNoeulerStress. Number.
limitationsNolimitations. Array.
slendernessNoslenderness. Number.
criticalLoadNocriticalLoad. Number.
criticalStressNocriticalStress. Number.
transitionSlendernessNotransitionSlenderness. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, openWorld, so the description's added value is the commercial and protocol behavior: a $0.02 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without running the calculation. That payment-gating disclosure is exactly the kind of context annotations cannot carry. It stops short of saying anything about convergence, unit conventions, or result interpretation.

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?

Three tight sentences with the computational purpose front-loaded, followed by price, endpoint, and payment-gating behavior. Nothing is redundant, though the phrasing is telegraphic ('with caller K') and could be slightly clearer without adding length.

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?

With an output schema present and annotations covering the safety profile, the description supplies the remaining critical unknowns: cost, transport, and failure behavior on unpaid calls. The main residual gap is the absence of any note on units or on the Euler/Johnson transition, but the core calling requirements are 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?

Schema description coverage is nominally 100%, so the baseline is 3. The description does add one piece of real meaning by tying K to the effective-length factor of a 'pin-ended equivalent column', but it says nothing about E, fy, A, I, or length, leaving the agent reliant on the schema's terse field descriptions.

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 computation: elastic Euler and inelastic Johnson-parabola critical stress/load for a pin-ended equivalent column, which clearly distinguishes it from the other structural siblings by being a dedicated column-buckling calculation. It is not just a restatement of the name, though it does not explicitly contrast itself with any sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives no when-to-use or when-not-to-use guidance, no prerequisites, and no explanation of when Euler versus Johnson governs the result (presumably internal, but unstated). The agent must infer applicability entirely from the tool name and the phrase 'pin-ended equivalent column'.

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.

Resources