Skip to main content
Glama

Battery pack nominal rating

bpj_bench_battery_pack_rating
Read-onlyIdempotent

Calculate nominal pack voltage, capacity, and watt-hours for identical cells in series and parallel.

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": {
      "cellV": "<cellV>",
      "cellAh": "<cellAh>",
      "series": "<series>",
      "parallel": "<parallel>"
    },
    "name": "bpj_bench_battery_pack_rating"
  }
}

Input Schema

NameRequiredDescriptionDefault
cellVYes
cellAhYes
seriesYes
parallelYes

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=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description needs to carry less. It adds the meaningful constraint that only identical cells are supported, but says nothing about the units of the returned values, the return shape, or edge behavior at the schema bounds. Useful but thin beyond annotations.

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 with the verb, the resource, the three outputs, and the configuration constraint. No filler, no repetition of schema or annotation content.

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 pure four-input calculator with no output schema, the description names what gets returned (voltage, capacity, watt-hours) and the modeling assumption, which is close to sufficient. The remaining gap is that it does not confirm the result is a single computed object rather than three separate values, or the output units.

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 burden falls on titles plus the prose. The description conveys the physical model ('in series and parallel') that gives meaning to the series/parallel parameters, and 'identical cells' clarifies that one cellV/cellAh pair represents every cell. It does not state which parameter drives which output (series multiplying voltage vs parallel multiplying capacity), which is the key semantic an agent would want.

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 states a concrete verb ('Calculate') and names the exact outputs (nominal pack voltage, capacity, watt-hours) plus the configuration model (identical cells in series and parallel), so an agent knows precisely what is computed. It is distinguishable from a runtime estimator like bpj_bench_battery_runtime by the 'nominal rating' framing, 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?

Usage is only implied: the phrase 'identical cells' establishes the precondition that all cells must be the same part, which effectively scopes when the tool applies. There is no explicit when-to-use/when-not-to-use statement and no routing to alternative pack tools, so the agent must infer applicability from domain knowledge.

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.