Skip to main content
Glama
gchen19

AnkusDrive

by gchen19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Random Vibration

random_vibration
Read-only

Compute random vibration response from modal frequencies and a PSD profile using Miles' equation to estimate RMS g, 3-sigma stress, and 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}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNo
analysisNo
psd_profileYes
frequencies_hzNo
allowable_stress_mpaNo
modal_stress_mpa_per_gNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses the calculation method (SDOF resonators, SRSS combination, exact formula), interpolation behavior (log-log, zero outside band), and consequences (mode stiffened above band escapes drive). It also explains optional stress conversion and pass/fail logic.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is dense but every sentence carries information: problem statement, input alternatives, PSD behavior, math model, optional stress outputs, and return structure. It is front-loaded with the core purpose and contains no filler.

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 tool with no output schema, the description provides the complete return object, formulas, defaults, and parameter semantics. Nothing an agent needs to decide whether to call it and how to interpret results is missing.

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 0%, and the description compensates fully: it explains analysis as a modal-run handle, frequencies_hz as an alternative, psd_profile with an example and interpolation behavior, q with default and rule of thumb, modal_stress_mpa_per_g conversion, and allowable_stress_mpa for pass/fail. Every parameter gains meaning.

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 opens with a specific verb and resource: computing a random-vibration response from a modal run using Miles' equation, explicitly noting it is closed-form and needs no external solver. This distinguishes it from sibling FEA/harmonic tools like fem_modal or harmonic_response without requiring schema inspection.

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?

It clearly states the input context: use after a fem_modal + fem_run analysis has produced natural frequencies, or supply an explicit frequency list, plus a PSD. It does not name sibling tools as alternatives or state explicit exclusion cases, but the modal-run and closed-form context makes intended usage 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