Skip to main content
Glama

Ideal LC resonance

bpj_bench_lc_resonance
Read-onlyIdempotent

Calculate lossless resonant frequency and characteristic impedance from inductance and capacitance.

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": {
      "inductance": "<inductance>",
      "capacitance": "<capacitance>"
    },
    "name": "bpj_bench_lc_resonance"
  }
}

Input Schema

NameRequiredDescriptionDefault
inductanceYes
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 readOnlyHint, idempotentHint, and non-destructive and closed-world behavior, so the description need not restate safety. It does add that the model is lossless and reports two named outputs, which is useful behavioral context. It still omits output units and the series-vs-parallel topology assumption, so the idealization is only partly disclosed.

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 sentence, front-loaded with the verb, with no redundant or filler wording. Nothing could be removed without losing information.

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?

There is no output schema, so the description should clarify return values; it names the two outputs but gives no units or formula/topology context. For a small two-parameter calculator this is just adequate, but it leaves the agent guessing about the series/parallel assumption and output dimensions.

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 should compensate, but it only says 'from inductance and capacitance' without adding units, ranges, or sign conventions. The units (uH, nF) appear only in schema titles, and the description adds no meaning beyond that.

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 set: calculate lossless resonant frequency and characteristic impedance. It clearly differs from siblings such as bpj_bench_rc_response or bpj_bench_rl_transient by naming LC resonance, though it never explicitly names an alternative.

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 or when-not-to-use guidance, no mention of prerequisites, and no reference to alternative tools. The word 'lossless' implies an idealized case, but the agent is left to infer that real-world ESR or load effects are out of scope.

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.