Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Apply load combination factors

structural-calcs_load-combinations
Read-onlyIdempotent

Combine caller load-case results with caller factors and report the governing combination per result key. Price $0.01 USDC. POST /api/v1/structural-calcs/load-combinations. 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": {
      "cases": "<cases>",
      "combinations": "<combinations>"
    },
    "name": "structural-calcs_load-combinations"
  }
}

Input Schema

NameRequiredDescriptionDefault
casesYescases, object. Required.
governByNogovernBy, string, one of absolute, max, min. Required.absolute
combinationsYescombinations, array. Required.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
governingNogoverning. Object.
limitationsNolimitations. Array.

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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the pricing model ($0.01 USDC) and, importantly, the failure behavior of an unpaid call — that it returns x402 payment terms and does not execute. That is exactly the kind of non-obvious behavioral trait descriptions should carry.

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 actual operation before pricing and endpoint details. Every sentence carries distinct information with no repetition, though the endpoint path and price line are somewhat mechanical and could be tightened.

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 and annotations cover safety, so the description needn't explain return values, and the payment semantics are well covered. The notable gap is the governBy selector — the choice between absolute, max, and min materially changes which combination is reported, and neither the schema nor the description explains it. Otherwise adequate for a three-parameter read-only calculation tool.

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?

With 100% schema description coverage and only three top-level parameters, the schema does the heavy lifting, so the baseline of 3 applies. The description adds only the loose notion of 'caller factors' and 'per result key'; it does not explain the governBy enum values (absolute, max, min), which is the one semantic detail the schema leaves entirely to the name alone.

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?

States a specific verb and resource: 'Combine caller load-case results with caller factors and report the governing combination per result key.' This is precise about both input ownership (caller-supplied cases and factors) and output shape (governing combination per result key), and it is distinguishable from every listed sibling, none of which perform combination logic.

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?

Implied usage is clear enough — you bring your own load-case results and factors — and the payment gate ('an unpaid call returns the x402 payment terms and does not run') is a genuinely useful operational condition. However, there is no explicit when-to-use versus when-not guidance, and nothing says what prerequisites the cases input must satisfy or how this relates to performing the underlying analysis first.

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