Skip to main content
Glama

Oscilloscope record window

bpj_bench_oscilloscope_record
Read-onlyIdempotent

Calculate time span between first and last acquired sample, horizontal time per division, and sample interval.

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": {
      "sampleRate": "<sampleRate>",
      "points": "<points>",
      "divs": "<divs>"
    },
    "name": "bpj_bench_oscilloscope_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
divsYes
pointsYes
sampleRateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3/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 safety and purity are covered structurally. The description adds that the tool derives three specific measurements, which is useful behavior context, but it omits units, output format, and any error behavior for out-of-range inputs.

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 tight sentence with no filler, and the three computed quantities are front-loaded. It could be marginally better structured by separating what is computed from what each input controls, 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 three-parameter calculator with no output schema, the description should at minimum pin down parameter roles and the units of the returned values. It covers the what-is-computed side adequately but leaves the input semantics and return units unexplained.

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% — the parameters carry only titles ("Horizontal divisions", "Record samples", "Sample rate (Hz)") and min/max bounds. The description names computed outputs rather than explaining how sampleRate, points, and divs feed those computations or how divs changes the per-division result, so it does not compensate for the documentation gap.

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 uses a specific verb ("Calculate") and names the exact three quantities produced: time span between first and last sample, horizontal time per division, and sample interval. This is clearly a pure-computation tool, but it makes no attempt to distinguish itself from other bench calculator siblings.

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 guidance on when to use this tool versus alternatives, no mention of prerequisites or constraints on inputs, and no indication of what a caller should do with the results. The domain (oscilloscope record window) implies usage but the description never states it.

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.