Skip to main content
Glama

Capacitor hold-up time

bpj_bench_capacitor_hold_up
Read-onlyIdempotent

Estimate capacitor hold-up under constant load current between given high and low voltages.

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": {
      "capacitance": "<capacitance>",
      "high": "<high>",
      "low": "<low>",
      "load": "<load>"
    },
    "name": "bpj_bench_capacitor_hold_up"
  }
}

Input Schema

NameRequiredDescriptionDefault
lowYes
highYes
loadYes
capacitanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact — that the model assumes constant load current between two voltage bounds — but says nothing about accuracy, assumptions about ESR/leakage, or what the returned quantity is.

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 key qualifier (constant load current) appears early. It is efficient, though its terseness leaves no room for the missing usage and return-value context.

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 simple deterministic read-only calculator this is close to adequate, but with no output schema the description should state what is returned (hold-up time, presumably in seconds) and any validity constraints. As written, an agent knows what to compute but not exactly what comes back.

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 partially does by clarifying that 'load' is a constant current and that 'high'/'low' are the voltage bounds the discharge runs between. Units (V, mA, uF) come only from schema titles, and edge behavior (e.g. low >= high, low = 0) is not addressed, leaving a real compensation gap.

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 ('Estimate') and resource ('capacitor hold-up') plus the governing conditions (constant load current, between high and low voltages), which is enough to distinguish it from siblings like bpj_bench_rc_response or bpj_bench_battery_runtime. It stops short of explicitly naming an alternative tool, so it sits just below a 5.

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 statement of when to choose this tool over the many other bench/transient calculators in the sibling list, nor any exclusions or prerequisites. The only guidance is implicit in the phrase 'constant load current', which hints at the modeling regime but does not tell the agent when that regime applies.

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.