Skip to main content
Glama

Sabine reverberation estimate

bpj_eng_room_reverb
Read-onlyIdempotent

Estimate Sabine RT60 in a diffuse room from volume and equivalent absorption area.

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": {
      "volume": "<volume>",
      "absorption": "<absorption>"
    },
    "name": "bpj_eng_room_reverb"
  }
}

Input Schema

NameRequiredDescriptionDefault
volumeYes
absorptionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered; the description adds that this is an estimate for a diffuse room, which signals a modelling assumption. It does not disclose the return unit (seconds), the formula used (RT60 = 0.161V/A), or accuracy limits.

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; inputs and output are stated in one pass and every word earns its place.

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 two-parameter formula tool with annotations covering safety, the definition is nearly sufficient, but with no output schema it should state what comes back (RT60 in seconds) and note the diffuse-field assumption or typical valid absorption range. Those omissions are real for an engineering calculation tool.

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%, but the two parameters carry titles giving units (m3 and m2), so the schema itself carries most of the meaning. The description only restates 'volume' and 'equivalent absorption area' without adding semantics such as whether absorption is total Sabine area versus an average coefficient.

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?

Names a specific verb plus resource ('Estimate Sabine RT60') and the exact inputs, so an agent can distinguish it from the other engineering calculators. It stops short of distinguishing itself from a sibling like bpj_eng_room_air_changes by naming the alternative, but the physics purpose is unambiguous.

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 prerequisites, and no mention of the diffuse-field/Sabine validity condition under which the estimate is acceptable. The agent must infer applicability purely from the formula 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.