Skip to main content
Glama

Hertz Contact

hertz_contact
Read-only

Calculate Hertzian point-contact peak pressure, contact radius, and approach for sphere-on-flat or sphere-on-sphere loading to screen designs before a nonlinear FEM contact solve.

Instructions

Exact Hertzian point-contact peak pressure (NO solver) — the screening twin of a frictional CONTACT PAIR solve. Sphere of radius_mm on a flat (default) or on a second sphere radius2_mm (negative for a conforming socket). Each body's elastics from youngs#_gpa+poisson# or a Materials-DB material#; body 2 defaults to body 1. Reduced modulus 1/E = (1−ν₁²)/E₁ + (1−ν₂²)/E₂, effective radius 1/R = 1/R₁ + 1/R₂; contact radius a = (3FR/4E*)^(1/3), peak pressure p₀ = 3F/(2πa²) = 1.5× mean, approach δ = a²/R. Half-space theory: valid while a ≪ R and p₀ below first sub-surface yield (~1.6·σ_y) — past that escalate to the nonlinear fem_set_nonlinear_material contact path.

Returns {e_star_mpa, effective_radius_mm, contact_radius_mm, peak_pressure_mpa, mean_pressure_mpa, approach_mm, a_over_R, fidelity, band_pct, valid_range_ok, warnings, escalate_to}.

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>",
      "radius_mm": "<radius_mm>"
    },
    "name": "hertz_contact"
  }
}

Input Schema

NameRequiredDescriptionDefault
load_nYes
poisson1No
poisson2No
material1No
material2No
radius_mmYes
workspaceNoRun this call in this named workspace
radius2_mmNo
youngs1_gpaNo
youngs2_gpaNo

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

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

Annotations already declare `readOnlyHint: true` and `openWorldHint: false`; the description adds substantial behavioral context: no solver, half-space assumptions, validity range, warnings, and `escalate_to`. It also lists returned fields even though no output schema exists.

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?

The description is dense but front-loads the core purpose and has no obvious filler; every sentence contributes physics, input semantics, validity, or return details. It could be more scannable with structure, but the length is largely justified by the tool's complexity and low schema coverage.

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?

For a complex 10-parameter physics tool with no output schema, the description is unusually complete: it covers theory, defaults, validity limits, failure/escalation behavior, and the returned fields. It gives the agent enough context to invoke the tool correctly and interpret the result.

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 10% schema description coverage, the description carries most parameter meaning: `radius_mm`, `radius2_mm` including negative socket semantics, `youngs#_gpa` + `poisson#`, Materials-DB `material#`, and body-2 defaults to body 1. `load_n` and `workspace` are not explicitly explained, but their names are largely self-describing.

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 computation, 'exact Hertzian point-contact peak pressure (NO solver)', and positions it as the screening twin of a frictional contact pair solve. It distinguishes itself from the nonlinear contact path by naming `fem_set_nonlinear_material` as the escalation target.

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

Usage Guidelines5/5

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

It gives explicit usage context as a screening tool, defines validity limits (`a ≪ R`, `p₀` below first sub-surface yield), and states when to escalate to the nonlinear `fem_set_nonlinear_material` contact path. The default flat-vs-second-sphere behavior is also clear.

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