Skip to main content
Glama

Weld Group

weld_group
Read-only

Rates a planar fillet-weld group by Blodgett's line method, computing direct and torsional shear to size leg length or check throat stress against allowable.

Instructions

Rate a planar fillet-weld group by Blodgett's treat-weld-as-a-line method. segments=[((x1,y1),(x2,y2)),...] (mm); an in-plane force_n=[Fx,Fy] at load_point_mm=[px,py] gives direct shear f=F/L plus torsional f=Tr/J from the eccentric moment about the weld centroid, added vectorially at the worst end. required_leg = f_r/(0.707allowable); given leg_mm, throat stress f_r/(0.707*leg) is checked vs allowable. Returns {weld_length_mm, centroid_mm, Ix_mm3, Iy_mm3, J_mm3, direct_shear_n_per_mm, max_shear_n_per_mm, worst_point_mm, required_leg_mm, throat_stress_mpa?, shear_sf?, pass}. weld_type ('fillet' default) labels the group and selects the throat convention.

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": {
      "segments": "<segments>",
      "force_n": "<force_n>",
      "load_point_mm": "<load_point_mm>"
    },
    "name": "weld_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
leg_mmNo
force_nYes
segmentsYes
weld_typeNofillet
workspaceNoRun this call in this named workspace
load_point_mmYes
allowable_shear_mpaNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, consistent with a pure analytical call; the description reinforces this by describing the full mechanics (direct shear f=F/L, torsion f=T*r/J about the centroid, vectorial addition at the worst end) rather than side effects. It goes beyond the annotations by disclosing the exact formulas, the throat convention (0.707 factor) and the 'worst end' selection rule, though it omits any stated limitations such as planarity or 2D-only assumptions beyond the word 'planar'.

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?

Purpose and method are front-loaded in the first clause, then parameters and outputs follow in a tight, information-dense sequence with no filler. The terse physics notation is dense but every clause contributes a decision-relevant fact.

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?

There is no output schema, so the description correctly enumerates the return fields (weld_length_mm, centroid, Ix/Iy/J, direct and max shear, worst_point, required_leg, throat_stress, shear_sf, pass). For a 7-parameter structural calculation this is close to self-sufficient; the only gap is the unchecked allowable_shear_mpa default and the workspace plumbing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With only 14% schema description coverage, the description carries the load and does it well: it gives the format and units for segments, force_n, load_point_mm, the role of leg_mm (which toggles sizing vs checking), and weld_type's effect on throat convention. It is weaker on allowable_shear_mpa (referred to only as 'allowable', no unit or default) and never mentions the workspace parameter.

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+resource ('Rate a planar fillet-weld group') and names the exact method (Blodgett treat-weld-as-a-line), which no sibling tool does. An agent can immediately tell this is a weld-group stress calculation rather than a CAD modeling or generic FEM tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

The description makes the operating context explicit: an in-plane force at a load point over planar segments, with two clear modes ('required_leg = f_r/(0.707*allowable)' when sizing vs 'given leg_mm ... is checked vs allowable' when verifying). It does not state exclusions (e.g., out-of-plane loads, non-fillet welds, 3D weld lines), but no sibling is a close alternative that needs routing away.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools