Skip to main content
Glama

EE Ohm's Law Calculator

calculator_ee_ohms_law
Read-only

Solve V = I × R for any one missing quantity. Distinct from physics ohms-law tool.

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

Input Schema

NameRequiredDescriptionDefault
currentNoCurrent in amperes.
voltageNoVoltage in volts.
resistanceNoResistance in ohms.

Output Schema

NameRequiredDescriptionDefault
resultYes
formulaNo
expressionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, destructiveHint=false, so the safety profile is covered. The description adds only the weak hint that exactly one quantity should be missing; it says nothing about error or ambiguity handling when zero or multiple inputs are given, which is the real behavioral risk given required=[].

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?

Two sentences, zero waste, with the formula and the missing-quantity rule front-loaded ahead of the sibling disambiguation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no explanation, and the operation is simple. However, for a tool where every parameter is optional, the description should state the 'supply exactly two of three' contract explicitly and describe error behavior — that omission leaves a real gap.

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 description coverage is 100% — voltage/current/resistance each carry units and examples — so the schema does all the work. The description's 'any one missing quantity' conveys the two-of-three constraint but adds no syntax or unit detail beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (solve) and a specific formula (V = I × R), and explicitly claims distinctness from another ohms-law tool. The sibling is named calculator_ohms_law while the description calls it the 'physics ohms-law tool', so the mapping requires a small inference, but the agent can still tell the two apart.

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?

'Solve for any one missing quantity' implies the user supplies exactly two of the three inputs, which is useful usage context. But it never states when to pick this over calculator_ohms_law, nor what happens with zero, one, or three parameters supplied (all three are optional).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.