Skip to main content
Glama

Wear Estimate

wear_estimate
Read-only

Calculate sliding wear volume loss and mean depth using Archard's equation; supply a wear coefficient or material pair, with hardness defaulting to the softer material.

Instructions

Estimate sliding wear (Archard): V = k·F·s/H. k (wear_coef) is empirical — pass it, or it's looked up by the material_pair's category pair (order-of- magnitude). H (hardness_mpa) defaults to Tabor 3·σ_y of the softer member. With apparent_area_mm2 a mean depth is reported and gated by max_depth_mm. Returns {wear_coef, hardness_mpa, volume_loss_mm3, depth_loss_mm, coef_basis, hardness_basis, pass}.

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": {
      "load_n": "<load_n>",
      "sliding_dist_m": "<sliding_dist_m>"
    },
    "name": "wear_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
load_nYes
wear_coefNo
workspaceNoRun this call in this named workspace
hardness_mpaNo
max_depth_mmNo
material_pairNo
sliding_dist_mYes
apparent_area_mm2No

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

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

Annotations only declare readOnly/openWorld, so the description carries real weight and does: it discloses the empirical nature of k, the order-of-magnitude lookup by category pair, the Tabor default for H, and the gating of depth by max_depth_mm. This is substantive behavioral context beyond the annotation.

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?

Dense but front-loaded: formula first, then parameter fallbacks, then outputs. Every clause earns its place, though the prose is terse enough that 'order-of-magnitude' and 'category pair' require a little inference.

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?

No output schema exists, but the description enumerates the returned fields (including coef_basis, hardness_basis, pass), and covers defaults and gating. An agent has enough to invoke it correctly, with only minor ambiguity around units of load_n and the exact material_pair format.

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 coverage is only 13%, so the description must compensate and largely does: it explains wear_coef, material_pair (category-pair lookup), hardness_mpa (Tabor 3·σ_y default), and apparent_area_mm2/max_depth_mm behavior. load_n and sliding_dist_m are only implied by the formula, leaving a small gap.

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 (Estimate) plus resource (sliding wear via Archard) and even gives the governing equation V = k·F·s/H. An agent can unambiguously tell this apart from analytic siblings like h_estimate or hertz_contact.

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?

Provides conditional usage for optional params (pass wear_coef, else it's looked up by material_pair; hardness defaults to Tabor) which implicitly tells the agent when to supply vs omit inputs. However, it never states when to reach for this tool over the many other analytic checks, nor any prerequisites like required material data.

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