Skip to main content
Glama
tresor4k

macalc

calculate_reverb_predelay

Calculate optimal reverb pre-delay using room length in meters and musical tempo in BPM to snap pre-delay to the musical grid.

Instructions

Calculate optimal reverb pre-delay based on room size and musical tempo. See list_bundles for related 'musique' calculators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
room_length_mYesRoom length in meters
bpmNoTempo in BPM (used to snap pre-delay to musical grid)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoComputed result. Object whose fields depend on the tool (e.g. {tax, marginal_rate, brackets} for tax tools, {volume_l, gallons} for volume tools).
formulaNoHuman-readable formula or method used (e.g. "I=P·r·t", "Magnus formula").
sourceNoAuthoritative source for the rule or formula (e.g. "Article 197 CGI", "NF DTU 21").
reference_urlNoLink to a calcul2 page documenting the calculation in detail.
Behavior2/5

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

No annotations exist, so the description must provide behavioral transparency. It does not disclose whether the tool is read-only, has side effects, or requires specific permissions. The 'calculate' action implies a non-destructive operation, but this is not explicitly stated.

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?

Two concise sentences. First sentence states purpose and inputs. Second sentence points to related calculators. No redundant or extra information.

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?

Given the tool has output schema and few parameters, the description covers the essential purpose. However, it could briefly mention the output unit or formula. Still, it is sufficiently complete for a simple calculator.

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 100% with descriptions for both parameters. The description adds no additional meaning beyond what the schema already provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly specifies the tool calculates optimal reverb pre-delay using two inputs (room size and tempo). The verb 'calculate' and resource 'reverb pre-delay' are specific, and the mention of related calculators distinguishes it from siblings.

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?

Description implies usage context (when you have room size and tempo) and references list_bundles for related tools. Does not explicitly state when not to use this tool, but context is clear enough for an agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tresor4k/macalc-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server