Skip to main content
Glama

Resistor tolerance bounds

bpj_bench_resistor_tolerance
Read-onlyIdempotent

Find lower and upper resistance for a nominal value with a symmetric tolerance.

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": {
      "resistance": "<resistance>",
      "tolerance": "<tolerance>"
    },
    "name": "bpj_bench_resistor_tolerance"
  }
}

Input Schema

NameRequiredDescriptionDefault
toleranceYes
resistanceYes

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, idempotentHint, non-destructive and closed-world behavior, so the safety profile is covered. The description adds only the behavioral detail that the tolerance is applied symmetrically, and says nothing about the shape of the returned values or edge cases such as a 100% tolerance.

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?

One front-loaded sentence with no filler, and the key qualifier ("symmetric") appears before the noun it constrains. Nothing can be removed without losing meaning.

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 two-parameter pure calculator with no output schema, the description names what is returned (lower and upper resistance) and how the tolerance is interpreted, which is close to sufficient. It could be tightened by stating the formula or how tolerance is expressed, but an agent can call it correctly as written.

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 parameter meaning; it does partly by framing 'resistance' as the nominal value and 'tolerance' as a symmetric percentage. Units and ranges are only in the schema titles and constraints, and the exact arithmetic (nominal × (1 ± tolerance/100)) is left to be inferred.

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 specific verb and result ("find lower and upper resistance") applied to a specific resource (a nominal resistance with a symmetric tolerance), which is enough to distinguish it from the other bench calculators in the sibling list. It stops short of naming or contrasting any alternative tool, but the operation itself is unambiguous.

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 word "symmetric" implicitly scopes the tool to symmetric tolerances and rules out asymmetric cases, which is a weak form of when-to-use guidance. There is no explicit statement of prerequisites, exclusions, or when an agent should pick a different sibling calculator instead.

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.