Skip to main content
Glama

RC low-pass gain and phase

bpj_bench_rc_response
Read-onlyIdempotent

Find sinusoidal gain and phase of an unloaded first-order RC low-pass at a chosen frequency.

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>",
      "capacitance": "<capacitance>",
      "frequency": "<frequency>"
    },
    "name": "bpj_bench_rc_response"
  }
}

Input Schema

NameRequiredDescriptionDefault
frequencyYes
resistanceYes
capacitanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world, and non-destructive behavior, so the description need not repeat safety properties. It adds useful modeling assumptions ('unloaded', 'first-order', 'sinusoidal'), but it does not disclose the return format, units for gain or phase, or whether the result is linear gain versus decibels.

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?

The definition is a single front-loaded sentence with no filler. Every phrase contributes to identifying the calculation and its domain assumptions.

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-parameter calculator with no output schema, the description is minimally adequate: it names the outputs as gain and phase. However, it omits output units and does not explain how the three parameters enter the calculation, leaving some ambiguity for correct interpretation of results.

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%, and the description only mentions 'chosen frequency' while leaving resistance and capacitance to be inferred from 'RC'. The schema titles provide units for all three parameters, but the description adds no constraints, roles, or formula context beyond the bare model name.

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 resource: finding sinusoidal gain and phase of an unloaded first-order RC low-pass. The qualifiers 'unloaded' and 'first-order' help distinguish it from related RC tools such as settling or loaded-divider calculations. It does not explicitly name a sibling alternative, so it falls short of 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?

The definition implies the tool is used for sinusoidal frequency-response calculations, but it gives no explicit when-to-use or when-not-to-use guidance. It does not point to alternatives such as RC settling or loaded divider tools, leaving the agent to infer selection from the purpose statement alone.

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.