Skip to main content
Glama

Dipole Resonance

dipole_resonance
Read-only

Calculate a thin center-fed half-wave dipole's first resonance from length or target frequency, returning a banded closed-form estimate for FDTD S11 sweep gating.

Instructions

Thin centre-fed half-wave dipole first resonance (NO solver, banded) — the closed-form twin the openEMS FDTD S11 antenna sweep (em_fullwave_submit) is gated against. Give EXACTLY ONE of length_mm (→ resonant frequency) or freq_ghz (→ resonant length). End-effect shortening k = shortening makes the resonant length a little under λ/2: L = k·λ, f_r = k·c/L (k≈0.48 textbook; ≈0.475 typical wire). Because k tracks the length/diameter ratio this is a ±band correlation (fidelity='banded', ~±3% over k∈[0.46,0.49]); an FDTD S11 sweep must put its first resonance inside [freq_lo, freq_hi] (or [length_lo, length_hi]).

Returns {given, shortening, half_wavelength_mm, resonant_length_mm, resonant_freq_ghz, freq_lo_ghz, freq_hi_ghz, length_lo_mm, length_hi_mm, fidelity, band_pct, valid_range_ok, warnings, escalate_to}.

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": "dipole_resonance"
  }
}

Input Schema

NameRequiredDescriptionDefault
freq_ghzNo
length_mmNo
workspaceNoRun this call in this named workspace
shorteningNo

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?

Annotations only declare readOnlyHint/openWorldHint; the description adds the substantive behavioral facts: no solver runs, results are a ±band correlation (fidelity='banded', ~±3% over k∈[0.46,0.49]), the exact model L = k·λ, f_r = k·c/L, and that a FDTD sweep must land its first resonance inside the returned [freq_lo, freq_hi]. It also discloses the returned fields, including `valid_range_ok`, `warnings`, and `escalate_to`, so the agent knows accuracy limits and failure surfacing up front.

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?

Front-loaded with the identity of the tool and the 'NO solver' constraint, and the exclusive-or parameter rule appears in the second sentence before the math. Dense but nearly all of it earns its place; the enumerated return-field list is long, though justified given there is no output schema.

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?

With no output schema, the description enumerates the return payload, defines the accuracy band and its validity condition, and explains the downstream gate relationship to the FDTD sweep. An agent has everything needed to call it correctly and to interpret fidelity='banded' rather than treating the number as exact.

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 only 25% (only `workspace` is described in the schema), so the description carries the burden and does: `length_mm` maps to resonant frequency and `freq_ghz` maps to resonant length, they are mutually exclusive, and `shortening` is defined as the end-effect factor k with its formula and typical values (0.48 textbook, ~0.475 wire, valid band [0.46,0.49]). This is far more than the bare numeric schema provides.

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 ('thin centre-fed half-wave dipole first resonance') and immediately constrains it with '(NO solver, banded)', which separates it from the solver-based sibling `em_fullwave_submit`. Also names the exact output quantity (resonant frequency or resonant length) and the physics model used.

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?

Explicitly says 'Give EXACTLY ONE of `length_mm` or `freq_ghz`', which is the key selection rule, and explains its role as the closed-form gate for the `em_fullwave_submit` FDTD sweep. It stops short of an explicit 'use this when you want a quick estimate, use the solver when you need accuracy' statement, so the alternative is implied rather than stated as a decision rule.

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