Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Analyse a 2D frame

structural-calcs_frame-2d-analysis
Read-onlyIdempotent

Euler-Bernoulli frame analysis with optional moment releases, nodal and member loads, returning displacements, reactions and member end forces. Price $0.05 USDC. POST /api/v1/structural-calcs/frame-2d-analysis. 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": {
      "nodes": "<nodes>",
      "members": "<members>"
    },
    "name": "structural-calcs_frame-2d-analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
nodesYesnodes, array. Required.
membersYesmembers, array. Required.
nodalLoadsNonodalLoads, array. Required.
memberLoadsNomemberLoads, array. Required.

Output Schema

NameRequiredDescriptionDefault
sourcesNosources. Array.
reactionsNoreactions. Array.
limitationsNolimitations. Array.
displacementsNodisplacements. Array.
memberEndForcesNomemberEndForces. Array.
conditionEstimateNoconditionEstimate. Number.

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?

Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), so the description's real contribution is the payment behavior: a $0.05 USDC cost, a POST endpoint, and the fact that an unpaid call returns x402 terms without running. That is exactly the kind of context annotations cannot express, though the response format is only partially described.

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: what it computes and returns, what it costs, and the endpoint/payment failure mode. The technical content is front-loaded and nothing is redundant, though the bare URL is of limited use to an agent.

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?

For a four-parameter analysis tool with an output schema and full annotation coverage, the description supplies the missing pieces — physical model (Euler-Bernoulli with releases), input categories, outputs, and payment semantics. Nothing critical is absent, though explicit routing against the truss/beam siblings would complete it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes further by naming the optional moment releases and the two load categories (nodal and member), telling the agent which parameter groups matter for a valid model. It does not add syntax or unit detail, which is left to 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?

The description states a specific method and resource — 'Euler-Bernoulli frame analysis' — with scope details (moment releases, nodal and member loads) that an agent can use to distinguish this from truss or beam analysis. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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 over structural-calcs_truss-2d-analysis or structural-calcs_beam-analysis, nor any statement of preconditions or exclusions. The word 'frame' implies the domain, but the agent must infer applicability entirely from the sibling names.

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