Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Eccentric weld-group force per length

structural-calcs_weld-group-analysis
Read-onlyIdempotent

Elastic line-weld analysis of an eccentrically loaded weld group returning maximum force per unit length. Price $0.02 USDC. POST /api/v1/structural-calcs/weld-group-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": {
      "lines": "<lines>",
      "load": "<load>"
    },
    "name": "structural-calcs_weld-group-analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
loadYesload, object. Required.
linesYeslines, array. Required.

Output Schema

NameRequiredDescriptionDefault
IpNoIp. Number.
lengthNolength. Number.
momentNomoment. Number.
sourcesNosources. Array.
centroidNocentroid. Array.
criticalNocritical. Array.
componentsNocomponents. Object.
limitationsNolimitations. Array.
maxForcePerLengthNomaxForcePerLength. Number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely non-obvious behavior beyond them: the $0.02 USDC price, the POST endpoint, and the fact that an unpaid call returns x402 payment terms instead of executing. It does not add anything about numerical assumptions or failure modes beyond the output 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 with the analytical purpose front-loaded, followed by cost and endpoint, then the payment failure mode. No wasted words, though the endpoint/price sentence reads as boilerplate repeated across a tool family rather than tool-specific content.

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?

Annotations and an output schema carry much of the burden, so the description need not explain return values. However, for an engineering calculation with nested coordinate inputs, the absence of any unit system (in/mm) or coordinate-frame statement is a meaningful gap an agent cannot resolve from the structured fields.

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 nominally 100%, so the baseline is 3, but the schema text is degenerate — 'x' is described identically to 'Px' as 'Px, number. Required.' The description does not compensate with any coordinate convention, point ordering, or unit system for the 'lines' endpoints and load point, which is the main semantic ambiguity here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific method (elastic line-weld analysis), a specific input condition (eccentrically loaded weld group), and a specific output (maximum force per unit length). The resource term 'line-weld' inherently distinguishes it from the sibling bolt-group tool without needing to name it.

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 only implied by the problem domain: an agent can infer it applies to weld groups under eccentric load, but there is no explicit when-to-use, when-not-to-use, or comparison against the bolt-group or section-properties siblings. The one concrete precondition stated is that an unpaid call does not run, which is a payment gate rather than selection 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