Skip to main content
Glama

Series Resistance Calculator

calculator_series_resistance
Read-only

R_total = R1 + R2 + ...

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": {
      "resistors": "<resistors>"
    },
    "name": "calculator_series_resistance"
  }
}

Input Schema

NameRequiredDescriptionDefault
resistorsYesList of resistances in ohms.

Output Schema

NameRequiredDescriptionDefault
expressionYes
equivalent_resistanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare this as a safe, read-only, closed-world calculator, so the description does not need to restate that. Beyond the formula, it adds no behavioral context such as input expectations, error behavior, or result format.

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?

The description is extremely short and front-loads the core formula with no wasted wording. Its brevity is efficient, though it borders on under-specification rather than being truly complete.

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 one-parameter calculator with an output schema and clear annotations, the formula is nearly sufficient. However, given many sibling calculators, the definition should do more to explain when this series-resistance calculation is the correct choice.

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 coverage is 100%, and the single parameter is already documented as 'List of resistances in ohms.' The description reinforces the series-sum relationship but adds little syntax or semantic detail beyond the schema.

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 name/title and the formula 'R_total = R1 + R2 + ...' make clear that this tool computes total resistance for resistors in series. It is more specific than a tautology, but it does not explicitly differentiate itself from the nearby sibling calculator_parallel_resistance.

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?

The description gives no explicit guidance on when to use this tool versus alternatives such as calculator_parallel_resistance or calculator_ee_resistor. Series usage is only implied by the tool name and formula.

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.

Resources