Skip to main content
Glama

EM DC Resistance

em_dc_resistance
Read-only

Calculate exact DC resistance of a uniform conductor from length, area, and conductivity or conductor name; add voltage to also compute current and Joule power.

Instructions

Exact DC resistance of a uniform conductor (NO solver) — R = L/(σ·A), the closed-form anchor the Elmer em_conduction_submit gate reproduces to machine precision. With voltage_v the Ohm/Joule pair is included (I = V/R, P = V·I). σ from conductivity_s_m or a conductor name.

Returns {resistance_ohm, conductivity_s_m, length_m, area_m2, current_a?, joule_w?}.

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>",
      "area_mm2": "<area_mm2>"
    },
    "name": "em_dc_resistance"
  }
}

Input Schema

NameRequiredDescriptionDefault
area_mm2Yes
conductorNo
length_mmYes
voltage_vNo
workspaceNoRun this call in this named workspace
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.1/5.0
Behavior4/5

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

Annotations only assert readOnlyHint/openWorldHint=false, and the description adds real value beyond that: it discloses the exact formula, that it involves NO solver, that voltage_v triggers the Ohm/Joule pair (I=V/R, P=V·I), and how σ is sourced. Return values are enumerated. Only gap is the mm-input-to-m-output unit handling.

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 essential purpose and formula, then layered details. Dense but each sentence carries useful content; math notation is compact. Slightly heavy for its length but no wasted prose.

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?

No output schema exists, and the description fully enumerates the return dict, so that burden is met. Combined with the formula and conditional-output notes, an agent can call it correctly; only unit-conversion detail on length/area is missing.

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 coverage is only 17%, so the description must compensate. It meaningfully explains voltage_v (Ohm/Joule), conductivity_s_m vs conductor (σ source), and the formula clarifies length_mm/area_mm2 intent, but it leaves units (mm inputs vs m outputs) and the workspace parameter unexplained.

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 DC resistance of a uniform conductor') plus the closed-form formula R = L/(σ·A). The '(NO solver)' qualifier and the reference to em_conduction_submit sharply distinguish it from the solver-based siblings.

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?

Clearly frames the tool as the closed-form anchor that em_conduction_submit reproduces, which implies its role as a fast analytic check versus a full solve. It does not explicitly state 'use this instead of / alongside X under condition Y', so usage is strong but not spelled out as an explicit alternative pair.

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