Skip to main content
Glama

Harmonic Response Submit

harmonic_response_submit
Destructive

Submits an asynchronous harmonic forced-response sweep for a plane-stress cantilever, returning a job ID and FRF metrics for resonance, static, and Q-factor checks.

Instructions

Harmonic forced response (FRF) via Elmer StressSolve Harmonic Analysis (SIMULATION_NEXT Tier B2), asynchronous — a plane-stress cantilever driven by a harmonic tip traction, swept one quasi-static point + n_sweep points across ±span_pct% of its first resonance, with Rayleigh β tuned to damping_ratio at f₁. Requires ElmerSolver; when absent this returns {ok:false, reason, install} rather than raising.

Three gates from the in-phase (real) response: f1_ratio — Re(H) = 0 exactly AT resonance, so the swept tip response's sign-flip locates f₁ vs the Euler-Bernoulli beam_modal closed form (within ~2%, plane-stress vs beam theory); static_ratio — the quasi-static point vs the exact tip compliance F·L³/(3EI) (within ~5%); q_ratio — max|Re|/static vs Q/2 = 1/(4ζ), the exact SDOF light-damping identity (within ~15%, sweep-sampled). Cross-links harmonic_response (the SDOF oracle) and random_vibration (same Q). Also accepts a prepared case_dir.

Returns the degradation dict or {job_id, status, cache_hit}; poll job_result for {ok, f1_solved_hz, f1_eb_hz, f1_ratio, static_solved_m, static_exact_m, static_ratio, peak_over_static, q_factor, q_ratio, frf:[[f_hz, tip_re_m]], case_dir}.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "harmonic_response_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nxNo
nyNo
sifNocase.sif
n_sweepNo
poissonNo
case_dirNo
height_mNo
length_mNo
span_pctNo
workspaceNoRun this call in this named workspace
youngs_paNo
traction_paNo
damping_ratioNo
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. First observed

TDQS

A4.3/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it discloses the missing-ElmerSolver fallback, the asynchronous {job_id, status, cache_hit} return, the need to poll job_result, and the exact result fields including frf data. These details substantially reduce uncertainty for a destructive job-submission tool whose annotations only flag destructiveHint=true.

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 front-loaded with the tool's purpose and method, then moves through gates, cross-links, and return behavior. It is dense and technical but largely free of filler, though the long gate explanations and semicolon-heavy sentences reduce scanability.

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 complex 14-parameter FEM tool with no output schema, the description is quite complete: it explains the async job model, degradation fallback, result payload fields, and validation gates. Its main incompleteness is that most individual parameters are not semantically documented.

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

Parameters3/5

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

Schema description coverage is only 7%, so the description must carry most parameter meaning. It explains the physical role of span_pct, n_sweep, damping_ratio, case_dir, and the harmonic tip traction, but leaves many parameters such as nx, ny, sif, poisson, height_m, length_m, youngs_pa, traction_pa, density_kg_m3, and workspace without semantic detail.

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 verb and resource: harmonic forced response (FRF) via Elmer StressSolve, implemented as an asynchronous plane-stress cantilever sweep. It also distinguishes the tool from siblings by naming harmonic_response as the SDOF oracle and random_vibration as sharing the same Q.

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 gives clear operational context: the call is asynchronous, the agent should poll job_result, a prepared case_dir is accepted, and ElmerSolver absence produces a degradation dict rather than an exception. The cross-links imply when to prefer this FEM path over the SDOF harmonic_response oracle, though it does not state explicit when-not-to-use rules.

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