Skip to main content
Glama

Fracture Check

fracture_check
Read-only

Calculate linear elastic fracture mechanics stress intensity versus material toughness to return safety factor, margin, and critical crack length for crack safety checks.

Instructions

Rate brittle fracture (LEFM): K = Y·σ·√(π·a) vs K_IC. a is crack length in mm; Y (geometry_factor) defaults 1.12 (edge crack), 1.0 for a centre crack. K_IC from the material (or override). Critical crack a_c = (K_IC/(Y·σ))²/π. Returns {k_applied_mpa_sqrt_m, k_ic_mpa_sqrt_m, geometry_factor, safety_factor, margin, critical_crack_mm, pass}; a crack past a_c gives SF<1 and margin<0.

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": {
      "stress_mpa": "<stress_mpa>",
      "crack_len_mm": "<crack_len_mm>"
    },
    "name": "fracture_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNoSteel-1045
workspaceNoRun this call in this named workspace
stress_mpaYes
crack_len_mmYes
geometry_factorNo
fracture_toughness_mpa_sqrt_mNo

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.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses the governing equation, default geometry factor values, material-derived K_IC with override behavior, critical crack formula, and the exact returned fields. It also explains the SF<1 and margin<0 failure condition, making the tool's behavior highly transparent.

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?

The description is dense but front-loaded with the core formula and meaning, followed by defaults, critical crack definition, and return fields. Every clause adds technical value, and there is no wasted prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description lists the returned keys and their meaning, including units in the field names. For a specialized fracture check, it provides enough context on inputs, defaults, calculation, and pass/fail criteria to invoke and interpret the tool correctly.

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?

Schema description coverage is low at 17%, so the description must carry parameter meaning. It explains crack length in mm, geometry_factor defaults for edge vs centre cracks, and that K_IC comes from material or override, covering the key engineering parameters well. Only workspace is left to the schema, so a 4 is appropriate.

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 states a specific engineering calculation: brittle fracture assessment using LEFM with K = Y·σ·√(π·a) compared to K_IC. It clearly identifies the resource (fracture) and the action (rate/check), and the formula distinguishes it from siblings such as fatigue_check or general stress checks.

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?

The description implies the tool applies to brittle fracture with a known crack length and gives the pass/fail interpretation when a crack exceeds a_c. However, it does not explicitly state when to use this versus alternatives such as fatigue_check, nor does it list exclusions or assumptions.

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