Skip to main content
Glama

PCM recording storage

bpj_bench_pcm_storage
Read-onlyIdempotent

Calculate uncompressed interleaved PCM payload size from stored bits per sample, sample rate, channels, and duration.

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>",
      "storedBits": "<storedBits>",
      "channels": "<channels>",
      "seconds": "<seconds>"
    },
    "name": "bpj_bench_pcm_storage"
  }
}

Input Schema

NameRequiredDescriptionDefault
secondsYes
channelsYes
sampleRateYes
storedBitsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds no behavioral context beyond that: it does not state the unit of the result (bytes vs bits), whether any container/header overhead is included, or how fractional sizes are handled.

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?

A single front-loaded sentence with no filler; the resource and the four inputs are packed in without repetition or preamble.

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 four-parameter pure calculator, the definition is enough to select and call the tool, but with no output schema it should have stated what the returned value is and in what unit. That omission is the main completeness gap.

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 coverage is 0% (titles only), so the description carries weight, and it does map each of the four parameters to a named concept: stored bits per sample, sample rate, channels, duration. However, it never clarifies what 'stored bits' means versus effective bits, ignores the multiple-of-8 constraint that only appears in a schema title, and does not restate units for the inputs.

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 and resource: 'Calculate uncompressed interleaved PCM payload size' plus the four inputs. It is clearly distinguishable from the sibling bench calculators by topic, but it never explicitly separates itself from neighbours such as bpj_bench_oscilloscope_record or bpj_bench_audio_buffer_latency, which touch adjacent storage/latency concerns.

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?

No when-to-use or when-not-to-use guidance, no mention of prerequisites or alternatives. The description never says this is a pure offline computation with no side effects, nor does it direct the agent to a related sizing tool for compressed or non-interleaved formats.

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.