Skip to main content
Glama

Drop Impact

drop_impact
Read-only

Calculates drop-impact deceleration from a specified crush distance, or required crush stroke from a deceleration limit, using an exact energy balance without a solver.

Instructions

Drop/impact screen by exact energy balance (NO solver). Give crush_distance_mm (available cushion/crumple stroke) -> deceleration, OR deceleration_limit_g (fragility spec) -> required stroke — exactly one. G_avg = h/d exactly (mass cancels); g_peak = pulse_factor·G_avg with pulse bounding the shape: 'constant' (ideal crush, 1×) | 'linear_spring' (elastic, 2×) | 'half_sine' (π/2×). v = √(2gh). mass_g only adds peak_force_n and energy_j. fidelity='exact'; where the part is stressed, or what an edge/corner strike changes, is escalate_to='impact_dynamics_submit'.

Returns {drop_height_mm, impact_velocity_m_s, pulse, pulse_factor, crush_distance_mm, g_avg, g_peak, pulse_duration_ms, deceleration_limit_g, required_crush_mm, energy_j, peak_force_n, 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": {
      "drop_height_mm": "<drop_height_mm>"
    },
    "name": "drop_impact"
  }
}

Input Schema

NameRequiredDescriptionDefault
pulseNolinear_spring
mass_gNo
workspaceNoRun this call in this named workspace
drop_height_mmYes
crush_distance_mmNo
deceleration_limit_gNo

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.6/5.0
Behavior4/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 real behavioral context beyond that: no solver, fidelity='exact', mass_g only affects peak_force_n and energy_j, and a warnings/valid_range_ok/band_pct validity surface. It honestly discloses what the model does NOT capture (local stress, edge/corner strike), though it leaves the meaning of band_pct and the valid input ranges unspecified.

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 core rule is front-loaded and every clause is information-dense (formulas, mode exclusivity, escalation). The trailing brace-list of 16 return keys is somewhat heavy, but since no output schema exists it earns most of its space.

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 6-parameter tool with no output schema and sparse schema descriptions, the description supplies input semantics, output field names, and modeling limits. Gaps remain: acceptable input ranges, how pulse_duration_ms is derived, and what band_pct represents are not explained.

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

Parameters5/5

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

Schema coverage is only 17% and the pulse field has no enum in the schema, so the description carries the load: it defines both modes of crush_distance_mm and deceleration_limit_g, spells out pulse values with their factors ('constant' 1x, 'linear_spring' 2x, 'half_sine' π/2x), and states the limited role of mass_g. That is meaningful semantics far beyond the bare schema.

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 and resource ('Drop/impact screen by exact energy balance') and immediately frames it as a closed-form calculation rather than a solver. It also names the escalatory sibling (impact_dynamics_submit) for the cases this tool does not cover, so an agent can separate it from the many FEM/simulation siblings.

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?

Explicitly states the either/or input mode: give crush_distance_mm to get deceleration, or deceleration_limit_g to get required stroke, and 'exactly one.' It also names the condition for switching tools — where the part is stressed or the strike is edge/corner, use escalate_to='impact_dynamics_submit'.

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