Skip to main content
Glama

Sheet bend allowance

bpj_material_bend_allowance
Read-onlyIdempotent

Calculate neutral-axis bend allowance from bend rotation, inside radius, thickness, and a supplied K factor.

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": {
      "bend": "<bend>",
      "radius": "<radius>",
      "thickness": "<thickness>",
      "k": "<k>"
    },
    "name": "bpj_material_bend_allowance"
  }
}

Input Schema

NameRequiredDescriptionDefault
kYes
bendYes
radiusYes
thicknessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety needs no restatement. The description does add one meaningful behavioral fact: the K factor is 'supplied' rather than derived, so the agent knows it must source that value. It stops short of disclosing the formula variant used or the unit of the result.

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?

A single front-loaded sentence naming the operation and all inputs, with no filler or redundancy. Nothing can be removed without losing information.

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?

For a pure four-parameter math function with no output schema, the description should state what comes back and in what unit (mm, given radius/thickness unit titles). It implies a scalar allowance result but never confirms the return type or units, leaving a small but real gap for an agent composing downstream calculations.

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 0% schema description coverage, the description carries the burden, and it does enumerate all four inputs (bend rotation, inside radius, thickness, K factor) and clarify that K is caller-supplied. However, it adds no constraint, default, or unit information beyond the titles already in the schema, and says nothing about how K interacts with the neutral-axis calculation.

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 — 'Calculate neutral-axis bend allowance' — plus the exact inputs, so the operation is unambiguous and clearly distinct from siblings like bpj_material_sheet_metal_mass or the bpj_sheet_* geometry tools. It does not explicitly name an alternative, keeping it just below 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 Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus alternatives, no prerequisites, and no guidance on where the K factor should come from (table lookup, material spec, prior tool output). The purpose implies sheet-metal flat-pattern work, but the agent must infer that entirely.

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.