Skip to main content
Glama

DC resistive load

bpj_bench_ohmic_load
Read-onlyIdempotent

Calculate steady current and dissipated power of an ideal resistor at a specified DC voltage.

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": {
      "voltage": "<voltage>",
      "resistance": "<resistance>"
    },
    "name": "bpj_bench_ohmic_load"
  }
}

Input Schema

NameRequiredDescriptionDefault
voltageYes
resistanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds useful modeling context ('ideal', 'steady', 'DC'), but does not state units of the returned current/power, the formulas used, or how the schema bounds (1e-9 to 1e9 for both inputs) are enforced.

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?

One front-loaded sentence with no filler; the computed outputs and the operating condition are both stated immediately.

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?

For a two-parameter scalar calculation with strong annotations, the description covers what is computed and the ideal-DC assumption. With no output schema and no parameter descriptions in the schema, the omission of return units/format and input domain notes (nonzero, positive resistance) leaves gaps an agent must guess at.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It clarifies that 'voltage' means a DC steady value, which does help, but it says nothing about resistance beyond 'ideal resistor' and does not explain the units or the required nonzero minimum passed via the schema titles.

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?

The description names a specific verb+resource pair ('Calculate steady current and dissipated power of an ideal resistor at a specified DC voltage') and the 'ideal resistor / DC' qualifier implicitly separates it from siblings like bpj_bench_loaded_divider, bpj_bench_voltage_divider and bpj_bench_resistor_tolerance. It stops short of naming any sibling explicitly, so differentiation is inferred rather than stated.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to use this versus the many bench siblings (loaded divider, resistor tolerance, wire drop). The 'ideal resistor at DC' framing implies steady-state only, but no exclusions, prerequisites, or alternative routing are given.

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.