MCP Audio Inspector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| analyze_audio_fileB | Analyze a single audio file and extract comprehensive metadata |
| analyze_audio_batchB | Analyze all audio files in a directory |
| get_supported_formatsB | Get list of supported audio formats |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: analyzing a batch of files, analyzing a single file, and listing supported formats. No overlap or ambiguity.
All tool names follow the consistent snake_case verb_noun pattern (analyze_audio_batch, analyze_audio_file, get_supported_formats).
Three tools is well-scoped for an audio inspection server, covering batch analysis, single file analysis, and format querying without excess or deficiency.
The tool set fully covers the domain of audio file inspection: analyzing individual files, batch processing, and checking supported formats. No obvious gaps.