Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Analyse a 2D pin-jointed truss

structural-calcs_truss-2d-analysis
Read-onlyIdempotent

Direct-stiffness truss analysis returning member axial forces, support reactions and joint displacements. Price $0.04 USDC. POST /api/v1/structural-calcs/truss-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_truss-2d-analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
loadsNoloads, array. Required.
nodesYesnodes, array. Required.
membersYesmembers, array. Required.

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations, which only declare readOnly/idempotent/openWorld safety. The description adds the price ($0.04 USDC), the endpoint, and critically that an unpaid call returns x402 payment terms without running the analysis — a prerequisite an agent cannot get from structured fields. It stops short of stating what happens on an invalid or unstable model.

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: what it computes and returns, then cost, then endpoint, then the payment gate. Result shape is front-loaded and no sentence is filler relative to its job.

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?

The output schema covers return values and the annotations cover safety, so those gaps are legitimately omitted. But for a structural solver the description is silent on units, sign conventions, coordinate/support defaults, and stability requirements — omissions that materially affect whether a call succeeds, and none of which are covered elsewhere.

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 baseline of 3 applies. However, the schema prose is templated and partly wrong (the A parameter is described as 'E, number'), yet the description adds nothing about node/support conventions, member connectivity, or load sign conventions to compensate.

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 technique and resource: 'Direct-stiffness truss analysis', and enumerates the three result classes (axial forces, reactions, displacements). The 'pin-jointed truss' qualifier distinguishes it in principle from the frame-2d-analysis sibling, but the description never actually contrasts the two, so the differentiation is left implicit.

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 when-to-use guidance and no exclusions or alternatives named. The only conditional statement is about payment, not about selection between this truss analysis and the frame/beam siblings, so an agent must infer applicability from the name alone.

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