Skip to main content
Glama

Low-voltage indicator resistor

bpj_bench_series_led_drop
Read-onlyIdempotent

Calculate an ideal series resistor and its dissipation for a low-voltage DC indicator LED.

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": {
      "supply": "<supply>",
      "forward": "<forward>",
      "current": "<current>"
    },
    "name": "bpj_bench_series_led_drop"
  }
}

Input Schema

NameRequiredDescriptionDefault
supplyYes
currentYes
forwardYes

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 readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that the result is 'ideal' (no tolerance/derating modeling) and that dissipation is returned alongside the resistance, which is useful beyond the annotations. It omits what happens with degenerate inputs (e.g., forward drop ≥ supply yields a non-physical negative resistor) and specifies no return units.

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 purpose and the two outputs are stated immediately. Its brevity comes at the cost of the behavioral detail an agent needs, but nothing in it is wasted.

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 three-input calculator with no output schema, the description should at least imply the returned quantities and their units and note the forward-drop-below-supply prerequisite. It partially covers the return value by mentioning dissipation, but leaves units and edge-case behavior unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the schema contributes only titles with units ('DC supply (V)', 'Target LED current (mA)', 'LED forward drop (V)'). The description adds no meaning about these three inputs, their units, or the constraint relationship between forward drop and supply that determines validity.

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 ('Calculate') and a concrete resource ('an ideal series resistor and its dissipation') scoped to a low-voltage DC indicator LED. It is clearly distinct from siblings like voltage_divider or wire_drop, though it never names them for positive differentiation.

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 'low-voltage DC indicator LED' implicitly scopes applicability, and the schema bounds (supply ≤ 24 V, current ≤ 30 mA) reinforce it. However, there is no explicit when-to-use vs. when-not guidance nor a pointer to an alternative tool for other resistor calculations.

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.