Skip to main content
Glama

Acoustic travel delay

bpj_eng_sound_path_delay
Read-onlyIdempotent

Estimate one-way sound travel time and speed in dry air from path length and temperature.

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": {
      "path": "<path>",
      "air": "<air>"
    },
    "name": "bpj_eng_sound_path_delay"
  }
}

Input Schema

NameRequiredDescriptionDefault
airYes
pathYes

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 establish readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile needs no restatement. The description adds the 'dry air' applicability condition, which is genuine behavioral context, but says nothing about assumptions of the underlying model, accuracy limits at the schema's -30 to 50 C bounds, or what exactly is returned beyond the two named quantities.

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?

One sentence, front-loaded with the verb and the two outputs, with the medium qualifier in the right place. Nothing is padded, though the single sentence leaves no room for the applicability detail that would help an agent decide to call it.

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-function calculator with full annotation coverage and no output schema, the description is close to sufficient: inputs, outputs, and medium are all stated. The remaining gap is the absence of any validity-range or model-assumption note, which matters for a physics estimate with hard schema bounds.

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%, though titles carry units (m, C) and min/max bounds are present. The description compensates partially by naming both inputs and their physical meaning and by pinning the medium to dry air, but it adds no guidance on valid ranges, behavior at extremes, or the sign/domain of path length.

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 names a specific operation (estimate), a specific quantity (one-way sound travel time and speed), the input basis (path length and temperature), and a medium constraint (dry air). It is clearly distinguishable from acoustic siblings such as bpj_eng_room_reverb or bpj_eng_combined_sound_level, though it does not explicitly name an alternative to steer away from.

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 is implied by the stated quantities: use it when you need propagation time or speed of sound rather than level or reverberation. There is no explicit when-not-to-use statement, no mention of how it differs from the delay-related siblings (bpj_launch_delay_contribution, bpj_system_single_queue_delay), which are unrelated domains the agent must rule out on its own.

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.