Skip to main content
Glama

Non-inverting amplifier gain

bpj_bench_opamp_noninverting
Read-onlyIdempotent

Compute ideal closed-loop voltage gain and unsaturated small-signal output for a non-inverting amplifier.

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": {
      "feedback": "<feedback>",
      "ground": "<ground>",
      "input": "<input>"
    },
    "name": "bpj_bench_opamp_noninverting"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
groundYes
feedbackYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare a pure, idempotent, side-effect-free read, so the safety profile is covered. The description adds real behavioral context beyond them: the result is an ideal closed-loop gain plus an unsaturated small-signal output, which tells the agent the model ignores op-amp bandwidth, slew, and clipping. It does not state the return shape, units, or the conditions under which the output would be considered saturated.

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?

One front-loaded sentence with no filler and the key qualifiers (ideal, unsaturated, small-signal) packed in. It is efficient, though that efficiency comes partly from omitting the parameter and return details that would earn a higher mark.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A three-parameter computation tool with no output schema and 0% schema description coverage needs the description to explain inputs, formula, and returned quantities. It supplies none of these, leaving the mapping of 'ground' and 'feedback' to the gain equation entirely undetermined.

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 description must carry parameter meaning and it does not. The ambiguous 'ground' parameter is particularly risky — nothing explains it is the ground-leg resistance (R1) rather than a ground reference voltage, nor that gain follows 1 + feedback/ground. Neither the units convention nor the valid resistance range is echoed.

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?

Names a specific verb+resource pair (compute closed-loop gain / small-signal output) for a clearly identified circuit topology (non-inverting amplifier), which separates it from divider and transient siblings in the bench set. It stops short of stating the gain relation or how it differs from any specific alternative tool.

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 when-to-use guidance, no prerequisites, and no named alternative. An agent must infer from the title alone that this covers non-inverting topology only, and that inverting or loaded configurations are handled elsewhere.

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.