Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Compute cross-section geometric properties

structural-calcs_section-properties
Read-onlyIdempotent

Area, centroid, second moments, elastic/plastic moduli, radii of gyration and torsion constant for standard shapes or polygons with holes. Price $0.03 USDC. POST /api/v1/structural-calcs/section-properties. An unpaid call returns the x402 payment terms and does not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "structural-calcs_section-properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
holesNoholes, array. Optional.
outerNoouter, array. Optional.
shapeNoshape, string. Optional.
paramsNoparams, object. Optional.

Output Schema

NameRequiredDescriptionDefault
ANoA. Number.
JNoJ. Number.
IxNoIx. Number.
IyNoIy. Number.
SxNoSx. Number.
SyNoSy. Number.
ZxNoZx. Number.
ZyNoZy. Null.
rxNorx. Number.
ryNory. Number.
IxyNoIxy. Number.
JmethodNoJmethod. String.
sourcesNosources. Array.
centroidNocentroid. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses price ($0.03 USDC), the transport (POST /api/v1/structural-calcs/section-properties), and a non-obvious failure mode: unpaid calls return x402 payment terms and do not execute. That is real behavioral value not present in the structured fields; it does not cover units or validation behavior.

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 compact sentences, front-loaded with the computed outputs, then cost, then endpoint, then the payment failure rule. Dense but every clause carries information; no 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 not be explained, and pricing/transport are covered. However, with zero required parameters and a nested untyped 'params' object, an agent is left guessing how to compose a valid call (shape name vocabulary, units, outer/holes format), which the description does not address.

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 is nominally responsible for the four parameters; the description only gestures at them via 'standard shapes or polygons with holes', which maps loosely to shape vs. outer/holes. It adds no meaning about accepted shape names, coordinate ordering, or whether shape and outer are mutually exclusive, so it neither helps nor hurts beyond baseline.

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 resource (cross-section geometric properties: area, centroid, second moments, moduli, radii of gyration, torsion constant) and the input domain (standard shapes or polygons with holes). That is enough to separate it from sibling tools like beam-analysis or column-buckling, though it never explicitly contrasts with them.

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 phrase 'for standard shapes or polygons with holes', which signals the two input modes, but there is no explicit when-to-use/when-not-to-use guidance and no direction on which of the four optional parameters to supply. The only firm conditional given is the payment rule for unpaid calls.

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