Skip to main content
Glama

Beam Modal

beam_modal
Read-only

Compute exact Euler-Bernoulli natural frequencies for a uniform rectangular beam without a solver, providing a closed-form reference to validate FEM modal eigen-solves.

Instructions

Exact Euler-Bernoulli natural frequencies of a uniform rectangular beam — the closed-form modal oracle (no solver), and the band the CalculiX fem_modal eigen-solve is gated against. f_n = (βL)_n²/(2π)·sqrt(E·I/(ρ·A·L⁴)); the beam bends in height_mm (I = width·height³/12, so a slender beam's lowest mode is the thinnest-direction bend). boundary: 'cantilever' | 'simply_supported' | 'clamped_clamped' | 'free_free' | 'clamped_pinned' (up to 5 modes each). Material via youngs_gpa+density_kg_m3, or a Materials-DB material name. Slender-beam theory — accurate while length ≫ height (thick beams need a Timoshenko correction).

Returns {boundary, n_modes, frequencies_hz, beta_l, first_mode_hz, youngs_gpa, density_kg_m3, area_mm2, I_mm4, slenderness}.

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": {
      "length_mm": "<length_mm>",
      "width_mm": "<width_mm>",
      "height_mm": "<height_mm>"
    },
    "name": "beam_modal"
  }
}

Input Schema

NameRequiredDescriptionDefault
n_modesNo
boundaryNocantilever
materialNo
width_mmYes
height_mmYes
length_mmYes
workspaceNoRun this call in this named workspace
youngs_gpaNo
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.7/5.0
Behavior5/5

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

With `readOnlyHint: true` and `openWorldHint: false` already covering the safety profile, the description adds substantial behavioral context: closed-form/no solver, the exact formula, the bending-axis convention, supported boundary conditions, up to five modes, material sourcing options, and the slender-beam accuracy limitation. Nothing contradicts the annotations.

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 front-loaded and technical: purpose, formula, bending axis, boundary options, material options, accuracy caveat, and return fields. Every sentence contributes either selection guidance, parameter meaning, or behavioral limits.

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 9-parameter analytical tool with no output schema, the description is unusually complete. It documents the return object fields, computational model, material resolution paths, boundary conditions, mode count, accuracy domain, and relationship to the FEM sibling.

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 most of the parameter meaning. It explains `height_mm` as the bending direction, relates `width_mm` and `height_mm` to the area moment, uses `length_mm` in the slenderness constraint, enumerates `boundary` values, describes `material` as an alternative to `youngs_gpa`/`density_kg_m3`, and implies a mode limit for `n_modes`. Only `workspace` is not covered, though its schema description handles that.

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 computational resource and verb: exact Euler-Bernoulli natural frequencies for a uniform rectangular beam. It distinguishes itself from the sibling `fem_modal` by identifying itself as the closed-form modal oracle that the CalculiX eigen-solve is gated against.

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 positions the tool as a no-solver analytical oracle and references `fem_modal` as the FEM alternative it validates, which gives strong usage context. It also notes the slender-beam limitation requiring a Timoshenko correction for thick beams, but it does not explicitly phrase when to choose this over `fem_modal` or which sibling to use for non-oracle workflows.

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