Skip to main content
Glama

Bar Impact

bar_impact
Read-only

Computes St-Venant stress, contact duration, force, and rebound for a uniform bar striking a rigid wall end-on, including yield and bilinear plastic response.

Instructions

St-Venant bar impact, exact (NO solver): a uniform bar striking a rigid wall end-on. Face stress σ = ρ·c₀·v₀ with c₀ = √(E/ρ) — mass, area and length cancel, so only a slower strike or a softer/lighter material lowers it; contact lasts 2L/c₀ and the bar leaves stress-free at the strike speed (restitution 1). Past the yield velocity v_y = σ_y/(ρ·c₀) the face yields and a bilinear material (tangent_mpa) caps at σ_y + ρ·c_p·(v₀ − v_y), c_p = √(E_t/ρ). E and ρ from youngs_gpa/density_kg_m3 or a Materials-DB material (which also supplies yield). area_mm2 adds force_n. The closed-form twin impact_dynamics_submit is gated against; also the quick ceiling on what any strike at this speed can do to this material. Uniaxial-stress (slender bar) theory.

Returns {wave_speed_m_s, stress_mpa, elastic_stress_mpa, force_n, contact_duration_ms, rebound_velocity_m_s, yield_velocity_m_s, plastic, plastic_wave_speed_m_s, 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": {
      "velocity_m_s": "<velocity_m_s>",
      "length_mm": "<length_mm>"
    },
    "name": "bar_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
area_mm2No
materialNo
length_mmYes
workspaceNoRun this call in this named workspace
yield_mpaNo
youngs_gpaNo
tangent_mpaNo
velocity_m_sYes
density_kg_m3No

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. Addedv0.5.6

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and closed-world, but the description adds real behavioral context: no solver, exact closed form, applicability limited to uniaxial-stress slender-bar theory, restitution 1, elastic-to-plastic transition past v_y, and output flags valid_range_ok/warnings/escalate_to. It doesn't cover workspace behavior or failure modes explicitly, keeping it at 4.

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?

Front-loaded with the model definition and scoping before the formulas and the return list, which is necessary since there is no output schema. It is dense with notation (σ = ρ·c₀·v₀, c_p = √(E_t/ρ)) that is arguably more than an agent strictly needs to invoke it, but each clause informs sensitivity or validity.

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?

For a 9-parameter, no-output-schema analytic tool this is nearly complete: it covers the physical model, parameter sourcing, plastic behavior, validity limits, and enumerates all return fields with fidelity/band/escalation signals. Gaps are minor (material name format, behavior when neither material nor E/ρ is supplied).

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 only 11%, so the description carries the burden and largely does: it maps velocity_m_s and length_mm into the physics, explains that E and ρ come from youngs_gpa/density_kg_m3 or a material lookup (which also supplies yield), that tangent_mpa enables the bilinear plastic cap, and that area_mm2 adds force_n. Only workspace is left to the schema, leaving minor ambiguity about valid material-name values.

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 precise verb+resource+model: "St-Venant bar impact, exact (NO solver): a uniform bar striking a rigid wall end-on." It explicitly distinguishes itself from the sibling impact_dynamics_submit ("closed-form twin ... gated against") and names the governing relation, so an agent can identify it without opening the schema.

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?

Gives clear context for use (quick closed-form ceiling, "what any strike at this speed can do to this material") and names the alternative impact_dynamics_submit as the gated twin, plus an escalate_to return field. There is no explicit "when not to use" statement, so it stops just short of a 5.

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