Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Transformed composite section properties

structural-calcs_composite-section-transform
Read-onlyIdempotent

Modular-ratio transformed-section properties and stresses for multi-material sections, optionally cracked. Price $0.03 USDC. POST /api/v1/structural-calcs/composite-section-transform. 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": {
      "reference": "<reference>",
      "parts": "<parts>"
    },
    "name": "structural-calcs_composite-section-transform"
  }
}

Input Schema

NameRequiredDescriptionDefault
partsYesparts, array. Required.
momentNomoment, number. Required.
referenceYesreference, string, length 1 to 40. Required.
concreteCrackedNoconcreteCracked, boolean. Required.

Output Schema

NameRequiredDescriptionDefault
ItrNoItr. Number.
sourcesNosources. Array.
stressesNostresses. Array.
limitationsNolimitations. Array.
neutralAxisNoneutralAxis. Number.
modularRatiosNomodularRatios. Object.
transformedAreaNotransformedArea. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description goes beyond them by disclosing the per-call price ($0.03 USDC) and, importantly, that an unpaid call returns x402 payment terms without running the calculation — a behavior an agent cannot learn from annotations or schema.

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 short sentences, front-loaded with the computation, then cost, then the payment failure mode. Every sentence carries distinct information; nothing is padded.

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-value detail is not needed, and the payment path is well covered. However, for a multi-material section tool competing with section-properties, the absence of any guidance on input construction (units, sign convention, when 'cracked' applies) leaves a real gap.

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 all four parameters and the nested part fields are documented structurally; baseline is 3. The description adds only mild meaning — 'multi-material' maps to per-part E and 'optionally cracked' maps to concreteCracked — without explaining reference, moment, or the rectangle/polygon part model.

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 computation (modular-ratio transformed-section properties and stresses) on a specific resource class (multi-material sections, optionally cracked). This implicitly separates it from the single-material sibling structural-calcs_section-properties, but the sibling is never named, so the differentiation is left to inference.

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?

No statement of when to choose this over section-properties or beam-analysis, and no prerequisites or exclusions. The only usage-relevant fact given is 'optionally cracked', which is a parameter hint rather than routing guidance.

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