Skip to main content
Glama

Loaded divider voltage drop

bpj_bench_loaded_divider
Read-onlyIdempotent

Find loaded divider output and percentage drop when a specified load bridges the lower resistor.

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>",
      "upper": "<upper>",
      "lower": "<lower>",
      "load": "<load>"
    },
    "name": "bpj_bench_loaded_divider"
  }
}

Input Schema

NameRequiredDescriptionDefault
loadYes
lowerYes
upperYes
voltageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety and determinism are covered. The description adds that the load is connected across the lower resistor and that two quantities come back (output and percentage drop), but says nothing about assumptions such as an ideal source, units of the result, or behavior at extreme load values.

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?

A single sentence that front-loads the outputs and then the qualifying condition. Every clause carries information; nothing is redundant or padded.

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?

With no output schema, the description does state that two results are returned, which is the essential return-value information for a four-parameter calculator. It is nearly complete; only the formula assumptions and output units are left unstated, which are minor for a straightforward circuit calculation.

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 0%, but each parameter carries a title with units ('Upper resistance (ohm)', 'Voltage (V)', etc.), so naming is not the gap. The description's real contribution is telling the agent how 'load' is wired (bridging the lower resistor), which the schema cannot convey; however it adds nothing about the roles or constraints of upper/lower/voltage.

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 ('Find') and specific outputs ('loaded divider output and percentage drop'), plus the physical condition ('a specified load bridges the lower resistor'). This distinguishes it in substance from the unloaded bpj_bench_voltage_divider, though it never names that sibling explicitly.

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 phrase 'when a specified load bridges the lower resistor' implies the applicable situation, but there is no explicit statement of when to prefer this over the plain voltage divider tool, nor any exclusions or prerequisites. Guidance is inferable rather than stated.

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.