Skip to main content
Glama

scan_audio_folder

Scan an audio folder for loops and extract BPM, key, and role from filenames. Returns parsed metadata and a distribution summary to help select loops for a REAPER session.

Instructions

Walk a folder for audio loops and parse metadata from filenames.

Returns every audio file (.wav, .mp3, .flac, .aif, .aiff, .ogg, .m4a) with BPM, musical key, and role (kick / bass / pad / lead / fx / …) extracted from the filename. Plus a summary of distributions so the AI can quickly decide on a target BPM / key before picking loops.

Args: path: Absolute folder path (e.g., D:/Music Production/Chillstep Express). recursive: Walk subfolders too. Default True. max_files: Stop after this many files. Default 500; max 5000.

Returns a structure with:

  • folder: resolved absolute path

  • total_files: how many matched

  • truncated: True if max_files hit before end

  • summary: BPM / key / role distributions + parse-failure counts

  • loops: list of { path, filename, duration_sec, size_mb, parsed: { bpm, key, role } }

  • hint: a one-line suggestion for the AI's next call

Files without parseable metadata are still listed; their fields are null. Pair with transport_set_bpm + load_loops to turn the selection into a working REAPER session.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
recursiveNo
max_filesNo
Behavior4/5

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

With no annotations, the description fully discloses read behavior: walks folder, parses filenames, returns list and summary, handles unparseable files with null fields, and respects max_files with truncation flag. Could mention non-destructive nature, but overall transparent.

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?

Well-structured with summary, then args, then return details. Front-loaded with purpose. Minor redundancy in describing return structure twice, but overall concise for the amount of information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema, yet description fully documents return fields (folder, total_files, truncated, summary, loops, hint). Also provides integration advice. Complete coverage for scanning a folder.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has zero descriptions, but description fully documents each parameter: path with example, recursive default, max_files default and maximum. Adds concrete meaning beyond schema titles and types.

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?

Clearly states the tool walks a folder for audio loops and parses metadata from filenames. Lists supported file formats and extracted metadata (BPM, key, role), distinctly separating it from siblings like load_loops or detect_common_bpm.

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?

Explicitly mentions pairing with transport_set_bpm and load_loops to build a REAPER session, and explains that the summary helps AI decide on target BPM/key. Lacks explicit 'when not to use', but context is clear.

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/xDarkzx/Reaper-MCP'

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