Skip to main content
Glama

PWM resistive load averages

bpj_bench_pwm_average
Read-onlyIdempotent

Find average voltage, RMS, and power for a resistive load driven between zero and a positive PWM level.

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>",
      "duty": "<duty>",
      "resistance": "<resistance>"
    },
    "name": "bpj_bench_pwm_average"
  }
}

Input Schema

NameRequiredDescriptionDefault
dutyYes
voltageYes
resistanceYes

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that this is a pure computed result for a resistive load, but it does not clarify whether the reported power is average or RMS power, nor anything about output precision or units beyond naming the quantities.

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 front-loaded sentence naming the outputs first and the driving conditions second, with no filler or repeated annotation content. Nothing could be removed without losing scope information.

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?

For a three-parameter pure calculator with a well-annotated safety profile and no output schema, this is close to sufficient: the reader knows the three returned quantities and the physical setup. The only residual gap is the exact meaning of the power term, which is minor at this complexity.

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 the schema does carry titles with units (Duty cycle %, Voltage V, Resistance ohm) and numeric bounds. The description adds partial meaning — voltage is the PWM high level and duty spans zero to that level, resistance is the load — but does not define whether duty is a percentage or fraction, nor how voltage relates to average versus peak.

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?

Names a concrete verb ("Find") and concrete outputs (average voltage, RMS, power) for a specific resource (a resistive load under unipolar PWM). The PWM/zero-to-positive-level framing makes it distinguishable from waveform-RMS siblings like bpj_bench_sine_rms, though it does not explicitly call out any alternative by name.

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 "driven between zero and a positive PWM level" implicitly scopes the tool to unipolar PWM into a resistive load, which is useful selection context. However, it never states when to prefer this over a sibling such as bpj_bench_ohmic_load or bpj_bench_sine_rms, nor any exclusions or prerequisites.

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.