Skip to main content
Glama
Sign In
mainstage-mcp

mainstage-mcp

by ChristianLechner304
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

find_audio_files

Search any folder for audio files (mp3, wav, aiff, m4a) to locate backing tracks, optionally filtered by keywords from the song title or file name.

Instructions

Find audio files (mp3, wav, aiff, m4a, …) in a folder, e.g. backing tracks for a song.

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": {
      "directory": "<directory>"
    },
    "name": "find_audio_files"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoWords from the song title or file name
directoryYesFolder to search (any folder the user names)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It implies a read-only search but does not state whether the search is recursive, how results are ordered, what the limit does, or what the return format looks like.

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?

The description is a single, front-loaded sentence with no wasted words. It efficiently conveys the core purpose and an example use case.

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

Completeness2/5

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

For a tool with three parameters, no annotations, and no output schema, the description is incomplete. It omits important behavioral details such as recursion, result format, limit semantics, and query matching behavior.

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

Parameters2/5

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

Schema coverage is 67%, and the description adds little parameter-specific meaning beyond the schema. The 'limit' parameter is undocumented in both schema and description, and the description does not clarify query matching or directory scope beyond what the schema already says.

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 states a specific verb and resource: find audio files in a folder, with example extensions and a use case. It is clear what the tool does, though it does not explicitly differentiate itself from sibling search tools like find_sound or search_sounds.

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?

The example 'backing tracks for a song' implies a usage context, but there is no explicit guidance on when to use this tool versus alternatives. No when-not conditions or sibling comparisons are provided.

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

Deploy Server

Other Tools