Skip to main content
Glama

Sine peak-to-peak and RMS

bpj_bench_sine_rms
Read-onlyIdempotent

Compute AC-only RMS, total RMS, and signal extrema of a sine with DC offset.

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": {
      "vpp": "<vpp>",
      "offset": "<offset>"
    },
    "name": "bpj_bench_sine_rms"
  }
}

Input Schema

NameRequiredDescriptionDefault
vppYes
offsetYes

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 openWorldHint=false, so the safety profile is fully covered and the description needn't restate it. The description adds that three distinct quantities are produced (AC-only RMS, total RMS, extrema) and that the DC offset influences the result, but it does not state the underlying formulas, output units, or what happens at edge values such as very small vpp.

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 front-loaded sentence with no filler; the outputs are enumerated compactly. It is efficient, though the brevity borders on under-specification for a two-parameter calculation.

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 simple two-parameter, side-effect-free calculator with full annotations and no output schema, the description is largely sufficient: it names the inputs' domain (sine with DC offset) and the three returned quantities. The remaining gap — output units and the exact distinction between AC-only and total RMS — is minor but real for an agent reporting results.

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 the semantic load. It does tie 'DC offset' to the offset parameter, but 'vpp' is never explained in the description — the agent relies on the schema title 'Peak-to-peak (V)' — and no relationship between vpp and offset (e.g., how AC RMS is derived from vpp) is given. This partially compensates for the coverage gap but leaves the core parameter meaning to the titles.

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 names a specific verb ('Compute') and a specific resource ('AC-only RMS, total RMS, and signal extrema of a sine with DC offset'), which lets an agent identify the calculation without opening the schema. It does not explicitly contrast with the other bench calculators (e.g., bpj_bench_fft_bin_grid, bpj_bench_pwm_average), but the resource is narrow enough that confusion is unlikely.

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 pointer to an alternative tool for related calculations. The agent must infer that this is the right calculator purely from the resource name.

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.