Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Rectangular concrete section flexure

structural-calcs_concrete-rect-flexure
Read-onlyIdempotent

Nominal flexural strength of a singly or doubly reinforced rectangular section with caller stress-block parameters. Price $0.03 USDC. POST /api/v1/structural-calcs/concrete-rect-flexure. 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>",
      "d": "<d>",
      "As": "<As>",
      "fc": "<fc>",
      "fy": "<fy>",
      "beta1": "<beta1>",
      "alpha1": "<alpha1>",
      "epsCu": "<epsCu>"
    },
    "name": "structural-calcs_concrete-rect-flexure"
  }
}

Input Schema

NameRequiredDescriptionDefault
bYesb, number. Required.
dYesb, number. Required.
AsYesb, number. Required.
EsNoEs, number. Required.
fcYesb, number. Required.
fyYesb, number. Required.
phiNophi, value. Optional.
beta1Yesbeta1, number, from any to 1. Required.
epsCuYesepsCu, number, from any to 0.01. Required.
alpha1Yesalpha1, number, from any to 1.5. Required.
dPrimeNodPrime, number, from 0 to any. Required.
AsPrimeNoAsPrime, number, from 0 to any. Required.

Output Schema

NameRequiredDescriptionDefault
aNoa. Number.
cNoc. Number.
MnNoMn. Number.
epsTNoepsT. Number.
phiMnNophiMn. Null.
sourcesNosources. Array.
limitationsNolimitations. Array.
steelYieldsNosteelYields. Boolean.
classificationNoclassification. String.
compressionSteelYieldsNocompressionSteelYields. Null.

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 cover safety (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add context, and it does: it discloses the price ($0.03 USDC) and, importantly, that an unpaid call returns x402 payment terms without executing the calculation. That gating behavior is not derivable from annotations or schema and prevents a costly misread of an empty response.

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 commercial terms, then the x402 gating rule. No filler, and each sentence carries distinct information an agent needs.

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?

Output schema exists, so return values need no explanation, and the annotations are rich, so the description only needs to add the compute semantics and the payment gating, which it does. What remains thin is domain guidance on applying it versus neighbouring tools, a minor gap for a well-specified calculation endpoint.

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 parameter documentation is already handled, and the baseline is 3. The description adds only conceptual framing ('singly or doubly reinforced', 'caller stress-block parameters'), which maps to AsPrime/dPrime and beta1/alpha1/epsCu but adds no units, ranges, or formatting detail beyond the schema.

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 computational verb and resource: 'Nominal flexural strength of a singly or doubly reinforced rectangular section with caller stress-block parameters.' That clearly separates it from sibling tools like section-properties or beam-analysis. It stops short of naming a sibling, so it is a clear 4 rather than 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?

The phrase 'with caller stress-block parameters' implies you must supply beta1/alpha1/epsCu yourself rather than relying on defaults, and 'singly or doubly reinforced' implies when AsPrime/dPrime matter. There is no explicit when-to-use or when-not-to-use guidance relative to the other structural calc tools, so guidance is only implied.

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