Skip to main content
Glama

Battery runtime at constant load

bpj_bench_battery_runtime
Read-onlyIdempotent

Estimate runtime for a constant-power load after usable-depth and conversion-efficiency allowances.

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": {
      "energy": "<energy>",
      "usable": "<usable>",
      "efficiency": "<efficiency>",
      "load": "<load>"
    },
    "name": "bpj_bench_battery_runtime"
  }
}

Input Schema

NameRequiredDescriptionDefault
loadYes
energyYes
usableYes
efficiencyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/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 fully covered. The description adds that the result is an estimate adjusted by usable-depth and efficiency derating rather than raw energy/load division, which is useful. It does not state the output unit (hours, minutes) or how the allowances are combined.

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?

A single front-loaded sentence with no filler; the scope qualifier comes before the allowance detail. It is lean to the point of omitting cheap, high-value facts like output units, but nothing is wasted.

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 four-parameter deterministic calculator with annotations covering behavior and no output schema, the description says enough about the inputs' roles to call it correctly. The main residual gap is the unit and form of the returned runtime, which an agent would have to guess.

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%, so the description must carry the load; it does explain that 'usable' is a depth allowance and 'efficiency' a conversion allowance, and that load is constant-power. It never clarifies the percentage scale (0-100) for usable/efficiency or that energy is nominal Wh, leaving meaning to the schema titles alone.

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 gives a specific verb and resource ('Estimate runtime') plus the qualifying condition ('constant-power load') and the two correction factors applied. An agent knows exactly what computation this performs, though it does not contrast itself with nearby calculators such as bpj_bench_battery_pack_rating.

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 'for a constant-power load' implicitly scopes when this tool applies (versus constant-current or constant-resistance cases), but there is no explicit when-not guidance, no prerequisites, and no named alternative to route to.

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.