Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Analyse beam reactions, shear, moment and deflection

structural-calcs_beam-analysis
Read-onlyIdempotent

Euler-Bernoulli FEM for simply supported, cantilever, fixed and continuous beams with point, UDL, linear and moment loads. Price $0.04 USDC. POST /api/v1/structural-calcs/beam-analysis. 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": {
      "length": "<length>",
      "E": "<E>",
      "I": "<I>",
      "supports": "<supports>"
    },
    "name": "structural-calcs_beam-analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
EYeslength, number. Required.
IYeslength, number. Required.
loadsNoloads, array. Required.
lengthYeslength, number. Required.
pointsNopoints, integer, from 11 to 1001. Required.
supportsYessupports, array. Required.
settlementsNosettlements, array. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
diagramsNodiagrams. Array.
maxShearNomaxShear. Number.
maxMomentNomaxMoment. Object.
minMomentNominMoment. Object.
reactionsNoreactions. Array.
limitationsNolimitations. Array.
maxDeflectionNomaxDeflection. Object.
conditionEstimateNoconditionEstimate. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent and non-destructive, but the description adds genuinely non-inferable behavior: a $0.04 USDC charge, the POST endpoint, and the fact that an unpaid call returns x402 payment terms instead of computing. It does not state units, error behavior for inconsistent supports, or what happens with zero loads, so it falls short of full disclosure.

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 sentences, zero filler: capability first, then price, then endpoint and payment-gate behavior. Every sentence carries information an agent needs before calling.

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?

An output schema exists, so return values need no explanation, and the capability/payment picture is complete. However, for a 7-parameter engineering solver the omission of unit conventions and the absence of any pointer to a sibling alternative leaves real gaps for an agent assembling a call.

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 100%, so the baseline is 3; the description adds load-type vocabulary but repeats what the schema's oneOf already encodes. It does nothing to resolve the schema's garbled parameter text (E and I are both described as 'length, number'), and never states the unit system or how the supports array must be arranged for a continuous beam.

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?

Names a specific method (Euler-Bernoulli FEM) and resource (beams), and enumerates the supported configurations (simply supported, cantilever, fixed, continuous) plus load types (point, UDL, linear, moment). That is far more discriminating than the sibling tools (truss/frame/column-buckling), so an agent can route correctly on this sentence alone.

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 context is implied by the enumerated beam and load types, but there is no explicit when-to-use/when-not guidance and no mention of any sibling (e.g. frame-2d-analysis for multi-member frames, deflection-limit-check for code checks). The only conditional instruction given is about payment, not selection.

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