Skip to main content
Glama

BRAINIAC Structural Engineering Calculators

Check deflections against span ratios

structural-calcs_deflection-limit-check
Read-onlyIdempotent

Compare computed deflections with caller span/deflection limits and optional long-term multipliers. Price $0.01 USDC. POST /api/v1/structural-calcs/deflection-limit-check. 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": {
      "span": "<span>",
      "checks": "<checks>"
    },
    "name": "structural-calcs_deflection-limit-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
spanYesspan, number. Required.
checksYeschecks, array. Required.
absoluteLimitNoabsoluteLimit, value. Optional.

Output Schema

NameRequiredDescriptionDefault
resultsNoresults. Array.
sourcesNosources. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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. The description adds context the annotations cannot: a $0.01 USDC price, the POST endpoint, and the crucial fact that an unpaid call returns x402 payment terms and does not run. That last detail materially changes agent behavior. It does not discuss output shape, but an output schema exists, so the gap is minor.

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 with the core comparison front-loaded, followed by price, transport, and payment-gate behavior in decreasing order of importance. The endpoint path is arguably redundant with the tool name, but it is the only borderline sentence and nothing is padded.

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 three-parameter read-only calculation with a full input schema and an output schema, the definition covers purpose, cost, transport, and the unpaid-call failure mode. Remaining gaps, such as how the multiplier default of 1 is applied and what the result verdict looks like, are carried by the schemas.

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. The description adds domain meaning for one parameter by calling the multiplier 'long-term' (i.e., a long-term deflection multiplier), but says nothing about the structure of the checks array or the absoluteLimit parameter, so it does not meaningfully exceed 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 uses a specific verb and resource: 'Compare computed deflections with caller span/deflection limits and optional long-term multipliers.' That is enough to distinguish it from analysis siblings such as beam-analysis or column-buckling, which compute rather than check against limits. It stops short of naming an explicit alternative, so it is not a 5.

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 phrase 'caller span/deflection limits': you use it when you already have deflections and want a pass/fail against a span ratio. There is no explicit when-not guidance, no prerequisites, and no pointer to a sibling tool for the upstream computation that produces the deflections.

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