Skip to main content
Glama

Waveguide Cutoff

waveguide_cutoff
Read-only

Compute exact rectangular waveguide cutoff frequency and propagation regime analytically—no numerical solver needed. Provides closed-form reference values for validating full-wave simulations.

Instructions

Exact rectangular-waveguide cutoff frequency (NO solver) — the closed-form twin the openEMS FDTD full-wave solve (em_fullwave_submit) is gated against. Broad wall a_mm, narrow wall b_mm (default a/2, WR convention). mode is 'TE'/'TM'. f_c(m,n) = (c/2√εᵣ)·√((m/a)²+(n/b)²); dominant TE10 reduces to the EXACT f_c = c/(2a√εᵣ). Below f_c the guide is evanescent (axial β imaginary, nothing transmits), above it propagates with guided wavelength λ_g = 2π/β. With a probe freq_ghz the regime (propagating / evanescent), k, β, λ_g and (below cutoff) the exact attenuation α = √(k_c²−k²) are returned — α is what the FDTD solve's field probes are gated against (alpha_ratio).

Returns {mode, m, n, a_mm, b_mm, eps_r, cutoff_hz, cutoff_ghz, kc_per_m, next_mode_cutoff_ghz, single_mode_band_ghz, probe_freq_ghz, regime, k_per_m, beta_per_m, alpha_per_m, guided_wavelength_mm, 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": {
      "a_mm": "<a_mm>"
    },
    "name": "waveguide_cutoff"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_mmYes
b_mmNo
modeNoTE10
eps_rNo
freq_ghzNo
workspaceNoRun this call in this named workspace

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
Behavior5/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description adds substantial physics behavior beyond that: below-cutoff evanescence, guided wavelength formula, exact attenuation alpha, plus self-reported `fidelity`, `valid_range_ok`, `warnings`, and `escalate_to` fields. This tells the agent exactly how trustworthy and bounded the result is.

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: purpose and formula come first, return fields last. It is somewhat formula-heavy, but with no output schema the enumeration of return keys earns its place by documenting the return contract. Minor over-density, otherwise efficient.

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?

No output schema exists, and the description fully compensates by enumerating every return field and explaining regime, k, beta, lambda_g, and alpha. Combined with the annotation safety profile, an agent has everything needed to call it and interpret results.

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 coverage is low (17%) — only `workspace` is documented in the schema — yet the description explains a_mm/b_mm roles, the b=a/2 default convention, the 'TE<m><n>'/'TM<m><n>' mode string format, eps_r via the formula, and freq_ghz as an optional probe. This compensates well, though `workspace` handling is left to the 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+resource ('Exact rectangular-waveguide cutoff frequency (NO solver)') and immediately distinguishes itself from the sibling `em_fullwave_submit` it is gated against. It even gives the closed-form formula, so the agent knows precisely what computation happens.

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 makes the analytic-vs-numerical routing clear: this is the closed-form twin used to gate/validate the FDTD solve, and it names `alpha_ratio` as the comparison point. It stops short of explicitly saying 'when to prefer this over a full-wave solve' as a decision rule, but the context is strongly implied.

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