Skip to main content
Glama

Audio buffer latency

bpj_bench_audio_buffer_latency
Read-onlyIdempotent

Estimate buffering delay from queued equal-sized blocks and sampling rate, excluding driver and conversion delay.

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>",
      "frames": "<frames>",
      "blocks": "<blocks>"
    },
    "name": "bpj_bench_audio_buffer_latency"
  }
}

Input Schema

NameRequiredDescriptionDefault
blocksYes
framesYes
sampleRateYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the safety profile is fully covered. The description adds genuine behavioral context by framing the result as an estimate and stating that driver and conversion delay are excluded. It does not disclose the output unit (seconds vs. milliseconds) or the assumed uniform-block idealization beyond 'equal-sized'.

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 scope caveat ('excluding driver and conversion delay') is placed where it is most useful, immediately after the stated action.

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 pure-calculation tool with no output schema, the definition should at minimum state the unit and shape of the returned delay. It gives the formula ingredients and the scope exclusions but leaves the result's form unspecified, which is the main remaining 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 description coverage is 0%, so the description has to carry the burden, and it only partially does: it maps to 'blocks' and 'sampleRate' but never explicitly explains 'frames' (frames per block). The schema's own titles ('Frames per block', 'Queued blocks', 'Sample rate (Hz)') cover meaning, but the description should have compensated for the coverage gap and left the third parameter implicit.

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 ('Estimate') and a precise resource ('buffering delay'), and names the two dominant inputs (queued equal-sized blocks, sampling rate). It does not distinguish this from lookalike siblings such as bpj_bench_pcm_storage or bpj_bench_clock_drift, so it falls short of a 5.

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 context is implied by the wording ('buffering delay', 'excluding driver and conversion delay'), which implicitly tells the agent this is a pre-driver, first-order estimate. There is no explicit when-to-use statement, no reference to an alternative tool, and no stated preconditions beyond the exclusions.

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.