Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Eccentric bolt-group forces (elastic)

structural-calcs_bolt-group-eccentric
Read-onlyIdempotent

Elastic-method force distribution in an in-plane eccentrically loaded bolt group. Price $0.02 USDC. POST /api/v1/structural-calcs/bolt-group-eccentric. 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": {
      "bolts": "<bolts>",
      "load": "<load>"
    },
    "name": "structural-calcs_bolt-group-eccentric"
  }
}

Input Schema

NameRequiredDescriptionDefault
loadYesload, object. Required.
boltsYesbolts, array. Required.

Output Schema

NameRequiredDescriptionDefault
boltsNobolts. Array.
momentNomoment. Number.
sourcesNosources. Array.
centroidNocentroid. Array.
limitationsNolimitations. Array.
polarMomentNopolarMoment. Number.
maxBoltForceNomaxBoltForce. 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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety is covered structurally. The description adds genuinely non-redundant behavior: the $0.02 USDC price, the POST endpoint, and the fact that an unpaid call returns payment terms without running the calculation. It does not cover determinism, units, or failure modes for invalid geometry, but the payment gate disclosure is exactly the kind of context annotations cannot express.

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?

Four short sentences, front-loaded with the method and the physical problem, then the commercial and transport facts. Every sentence carries information an agent needs, and there is no filler. Minor redundancy between the title-style first sentence and the tool name keeps it from a 5.

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 definition is reasonably complete for invocation: purpose, endpoint, cost, and payment gate are all stated, and an output schema exists so return values need no explanation. For an engineering calculation, though, it omits units and sign conventions for the bolt coordinates and load components, which materially affects whether a correct call is made. That gap is the main thing left unexplained at this complexity level.

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 is 3 and the schema is nominally the source of truth. In practice the schema descriptions are degenerate ('Px, number. Required.' repeated for x, y, Px and Py), so the description does little to disambiguate that x/y are the load's eccentric coordinates and bolts is a list of [x, y] coordinates. The phrase 'in-plane eccentrically loaded' is the only hint the description contributes, and it is indirect.

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 gives a specific verb and resource: elastic-method force distribution in an in-plane eccentrically loaded bolt group. That is far more informative than the title alone and an agent can tell it is a bolt-group solver rather than a beam, column, or truss routine. It stops short of naming any sibling or stating the boundary case where another tool (e.g. weld-group analysis) would apply.

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 scope statement 'in-plane eccentrically loaded bolt group', which tells the agent the qualifying input condition. The description also states a real operational prerequisite: an unpaid call returns x402 payment terms and does not execute, which prevents a wasted invocation loop. However, there is no explicit when-not guidance and no comparison to any alternative tool for related bolt or connection checks.

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