Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Spread-footing bearing pressure

structural-calcs_footing-bearing-pressure
Read-onlyIdempotent

Soil bearing pressure under a rectangular footing with axial load and moments, including partial uplift. Price $0.03 USDC. POST /api/v1/structural-calcs/footing-bearing-pressure. 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": {
      "B": "<B>",
      "L": "<L>",
      "P": "<P>"
    },
    "name": "structural-calcs_footing-bearing-pressure"
  }
}

Input Schema

NameRequiredDescriptionDefault
BYesB, number. Required.
LYesB, number. Required.
PYesB, number. Required.
MxNoMx, number. Required.
MyNoMy, number. Required.

Output Schema

NameRequiredDescriptionDefault
exNoex. Number.
eyNoey. Number.
qMaxNoqMax. Number.
qMinNoqMin. Number.
sourcesNosources. Array.
withinKernNowithinKern. Boolean.
limitationsNolimitations. Array.
contactLengthBNocontactLengthB. Number.
contactLengthLNocontactLengthL. Number.
cornerPressuresNocornerPressures. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: the $0.03 USDC cost, the POST endpoint, and the fact that an unpaid call returns x402 payment terms without executing the calculation. It does not disclose units, sign conventions, or the uplift criterion used, which is the substantive behavioral gap.

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 the tool computes, followed by cost, endpoint, and the unpaid-call behavior. Nothing is redundant and no sentence is filler.

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 payment behavior is fully covered. However, for a structural engineering calculation, the absence of any unit or sign-convention statement (footing dimensions, load units, moment axis convention) leaves a real ambiguity that the description should have closed.

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 nominally 100%, so the baseline is 3, but the schema descriptions are defective: every property including L, P, Mx and My is described as 'B, number. Required.', which is actively misleading for four of five parameters. The description partially rescues this by indicating the tool takes a rectangular footing with an axial load and moments, implying B/L are plan dimensions and Mx/My are biaxial moments, but it never assigns units or signs.

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 the specific quantity computed (soil bearing pressure under a rectangular footing) and the loading case (axial load plus moments, including partial uplift), which is enough to tell it apart from sibling calcs like section-properties or retaining-wall-stability. It never states the verb explicitly ('computes'), but the resource and scope are unmistakable.

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?

There is no guidance on when to choose this tool versus alternatives, and no stated preconditions (e.g., that B/L are footing plan dimensions and P is an axial service load). The only conditional behavior described is the payment path, which is about billing, not about when the calculation is appropriate.

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