Skip to main content
Glama

RC step settling time

bpj_bench_rc_settling
Read-onlyIdempotent

Find the time constant and time to settle within a given relative error for a first-order RC step.

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>",
      "error": "<error>"
    },
    "name": "bpj_bench_rc_settling"
  }
}

Input Schema

NameRequiredDescriptionDefault
errorYes
resistanceYes
capacitanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety behavior needs no restating. The description adds value by stating the two computed outputs, but does not say whether settling time is derived as n·τ from the error, what assumption (single-pole, zero initial state) applies, or whether results are unit-normalized.

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?

A single sentence with no filler, front-loading the outputs before the circuit model. It is perhaps over-terse for a calculation tool that would benefit from one clause on the underlying relation, but nothing is wasted.

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 deterministic three-parameter calculation with full annotation coverage and no output schema, the definition is minimally adequate: it names the outputs but leaves the settling-time formula, initial conditions, and output units unspecified. An agent could call it, but cannot predict exact semantics of the returned values.

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 only gestures at 'a given relative error' without clarifying that error is a percentage relative to the final value or explaining resistance/capacitance units. The schema's own titles ('Allowed residual error (%)', 'Resistance (ohm)', 'Capacitance (uF)') do much of the work, but the description itself adds little.

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?

States a specific verb ('Find') and two concrete outputs (time constant and time to settle) scoped to a first-order RC step, which distinguishes it from a waveform/response tool. It stops short of naming or contrasting with the sibling bpj_bench_rc_response, so the differentiation relies on the agent reading the names.

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?

Usage is only implied: an agent can infer this is the tool for settling-time calculations on a first-order RC circuit, but there is no explicit statement of when to prefer it over bpj_bench_rc_response or bpj_bench_rl_transient, and no prerequisites or exclusions are given.

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.