Skip to main content
Glama

Independent sound level sum

bpj_eng_combined_sound_level
Read-onlyIdempotent

Sum two incoherent source levels measured at the same listening point on the same weighting scale.

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "bpj_eng_combined_sound_level"
  }
}

Input Schema

NameRequiredDescriptionDefault
aYes
bYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 re-invocation behavior are covered structurally. The description adds valuable domain preconditions that annotations cannot convey (incoherence, same point, same weighting). However, it never states that the result is a single combined dB level, which matters since there is no output schema.

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 sentence with no wasted words, front-loading the operation and then the physical conditions that make it valid. Nothing could be removed without losing required meaning.

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 two-parameter pure calculation with rich annotations and a fully typed schema, the description covers the risky part: the physical validity conditions. The remaining gap is the unspecified return value (a single summed level), which no output schema fills in, but that is a minor omission for a tool this simple.

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 parameter burden and it only partly does. It implies both inputs are dB levels on the same weighting scale and measured at one point, but it does not say the operation is order-independent or reconcile the schema's -100 to 200 bounds with a level-in-dB interpretation.

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 ('Sum') and a precisely scoped resource: two incoherent source levels measured at the same listening point on the same weighting scale. That distinguishes it functionally from siblings like bpj_eng_sound_path_delay or the generic sum tools, though it does not name an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear applicability conditions: the sources must be incoherent, measured at the same listening point, and on the same weighting scale. That is enough context to decide the tool applies, but it names no alternative for the coherent-source or different-point cases, so it stops short of full when/when-not routing.

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.