Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Cantilever retaining-wall stability

structural-calcs_retaining-wall-stability
Read-onlyIdempotent

Overturning, sliding and bearing checks for a cantilever retaining wall with Rankine or Coulomb active pressure. Price $0.03 USDC. POST /api/v1/structural-calcs/retaining-wall-stability. 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": {
      "geometry": "<geometry>",
      "soil": "<soil>",
      "concreteGamma": "<concreteGamma>",
      "baseFriction": "<baseFriction>"
    },
    "name": "structural-calcs_retaining-wall-stability"
  }
}

Input Schema

NameRequiredDescriptionDefault
soilYessoil, object. Required.
theoryNotheory, string, one of rankine, coulomb. Required.rankine
geometryYesgeometry, object. Required.
surchargeNosurcharge, number, from 0 to any. Required.
baseFrictionYestotalHeight, number. Required.
wallFrictionNowallFriction, number, from 0 to 40. Optional.
concreteGammaYestotalHeight, number. Required.
passiveIgnoredNopassiveIgnored, boolean. Required.
waterTableDepthNowaterTableDepth, value. Optional.

Output Schema

NameRequiredDescriptionDefault
KaNoKa. Number.
qToeNoqToe. Number.
qHeelNoqHeel. Number.
sourcesNosources. Array.
activeArmNoactiveArm. Number.
fsSlidingNofsSliding. Number.
activeForceNoactiveForce. Number.
limitationsNolimitations. Array.
eccentricityNoeccentricity. Number.
fsOverturningNofsOverturning. Number.
verticalTotalNoverticalTotal. Number.
resistingMomentNoresistingMoment. Number.
overturningMomentNooverturningMoment. Number.
withinMiddleThirdNowithinMiddleThird. Boolean.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorld, so safety is covered. The description adds genuinely useful behavior beyond that: the $0.03 USDC price, the POST endpoint, and the important fact that an unpaid call returns x402 payment terms and does not execute. It omits any note on result format or failure modes, which the presence of an output schema partly mitigates.

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, front-loaded with what is computed, then cost, then endpoint, then the payment-gate behavior. No filler and no repetition of structured fields.

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, rich annotations, and full schema coverage, the description only needs to carry purpose and payment mechanics, which it does. The remaining gap is minor: no statement of unit conventions or sign assumptions in the geometry inputs, which matters for a nested-object engineering calculation.

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 100%, so the schema documents all nine parameters and the baseline is 3. The description adds only marginal semantic value by naming Rankine/Coulomb active pressure, which contextualizes the theory enum but not the geometry, soil, or friction inputs.

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 names a specific verb set and resource: 'Overturning, sliding and bearing checks for a cantilever retaining wall with Rankine or Coulomb active pressure.' That is far more informative than the title alone and clearly separates it from siblings like footing-bearing-pressure. It does not explicitly say which sibling to use instead for adjacent footing or flexure problems, so it stops 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?

Usage is implied by the resource itself (a retaining-wall stability check), and the theory option is surfaced. However, there is no explicit when-to-use/when-not guidance, no mention of prerequisites such as units or the passiveIgnored default's effect, and no routing to alternatives like footing-bearing-pressure.

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