Skip to main content
Glama

EM Skin Depth

em_skin_depth
Read-only

Calculates exact AC skin depth and per-square surface resistance from frequency, conductivity, and relative permeability without using a solver.

Instructions

Exact AC skin depth (NO solver) — δ = √(2/(ω·μ₀·μ_r·σ)) plus the per-square surface resistance R_s = 1/(σ·δ); fields/current decay e^(−x/δ) into the conductor (~95% of induction heating deposits within 1.5·δ). σ from an explicit conductivity_s_m or a conductor name (copper, aluminum, silver, gold, brass, steel-mild, stainless-304).

Returns {skin_depth_m, skin_depth_mm, surface_resistance_ohm, angular_frequency_rad_s, conductivity_s_m, mu_r}.

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": {
      "frequency_hz": "<frequency_hz>"
    },
    "name": "em_skin_depth"
  }
}

Input Schema

NameRequiredDescriptionDefault
mu_rNo
conductorNo
workspaceNoRun this call in this named workspace
frequency_hzYes
conductivity_s_mNo

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.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, yet the description still adds real context: closed-form/deterministic behavior, the accepted conductor names, the two mutually substitutable conductivity sources, and the exact returned keys. It does not state precedence when both conductivity_s_m and conductor are supplied.

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 core formula and kept to two compact blocks (behavior, then returns). Dense but every sentence carries technical information; 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?

With no output schema, the description enumerates the return object keys itself, closes the 20% schema-coverage gap by listing conductor names, and gives the physics rule of thumb. Nothing an agent needs to call it correctly is missing apart from the minor workspace note.

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 only 20%, so the description must compensate, and it largely does: it enumerates the conductor names (copper, aluminum, silver, gold, brass, steel-mild, stainless-304) that the bare schema lacks, ties mu_r and conductivity_s_m to the formula, and explains frequency via ω. The workspace parameter and the conductivity-vs-conductor precedence are left unaddressed.

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 computation (exact AC skin depth via δ = √(2/(ω·μ₀·μ_r·σ))) plus surface resistance, and explicitly says 'NO solver', which separates it from the many EM simulation siblings such as em_field, em_fullwave_submit and em_induction_heating_submit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'NO solver' framing and the '~95% of induction heating deposits within 1.5·δ' note imply the analytic quick-estimate use case, but no sibling is named and no explicit when-to-use/when-not rule is given against the induction or field solvers.

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