Skip to main content
Glama

Random Vibration

random_vibration
Read-only

Calculates RMS acceleration and stress response to a base-acceleration PSD using modal frequencies and Miles’ equation, with optional allowable-stress pass/fail.

Instructions

Random-vibration response off a modal run (Miles' equation; closed-form, no external solver). Provide either analysis (a handle whose fem_modal + fem_run already produced natural frequencies) or an explicit frequencies_hz list, plus a base-acceleration PSD psd_profile ([{"hz":20,"g2_hz":0.01}, ...]; log-log interpolated, and zero outside its band so a mode stiffened above the band escapes drive). Each mode is an SDOF resonator with amplification q (default 10; rule of thumb Q≈√f_n), combined by SRSS: rms_g = sqrt(Σ (π/2)·f·W(f)·Q). With modal_stress_mpa_per_g the g response converts to RMS / 3-σ stress; add allowable_stress_mpa for a pass/fail.

Returns {rms_g, first_mode_hz, dominant_mode_hz, q, psd_band_hz, miles_grms_g, modes: [{mode, frequency_hz, psd_g2_hz, contribution_g, in_band}], rms_stress_mpa, three_sigma_stress_mpa, 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": {
      "psd_profile": "<psd_profile>"
    },
    "name": "random_vibration"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
analysisNo
workspaceNoRun this call in this named workspace
psd_profileYes
frequencies_hzNo
allowable_stress_mpaNo
modal_stress_mpa_per_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.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: discloses that PSD is log-log interpolated and zeroed outside its band (so stiffened modes escape drive), that modes are SDOF resonators combined by SRSS, the Q≈√f_n rule of thumb, and how stress conversion and pass/fail are triggered. This is exactly the extra behavioral context annotations cannot carry.

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: the core method and the input alternative appear in the first two sentences, with physics details and outputs after. The trailing field list is long, but with no output schema it is load-bearing rather than redundant.

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 7-parameter engineering calculation with no output schema and low schema coverage, the description supplies both the physical model and the full return shape ({rms_g, miles_grms_g, modes[...], three_sigma_stress_mpa, pass}), leaving nothing an agent needs in order to call it or interpret the result.

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?

With only 14% schema description coverage, the description compensates almost fully: it explains the analysis-vs-frequencies_hz alternative, gives the psd_profile element format with an example, states q's default of 10 and the √f_n heuristic, and explains how modal_stress_mpa_per_g converts g to 3-σ stress and what allowable_stress_mpa adds. Only `workspace` is left to its own schema description.

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+resource — computes random-vibration response from a modal run via Miles' equation — and explicitly frames it as closed-form with no external solver, which distinguishes it from the fem_* solver siblings and harmonic_response.

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?

Declares the prerequisite path clearly: supply either an `analysis` handle whose fem_modal + fem_run already produced natural frequencies, or an explicit `frequencies_hz` list. It implies the fast closed-form alternative to a solver submission, but never explicitly contrasts itself with harmonic_response or fem_run when a full solve is warranted.

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