loudcheck
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_loudnessA | Loudness compliance verdict for a media file against a formal published standard. Measures integrated loudness, loudness range, and true peak (via ffmpeg), then evaluates them against the named standard's targets and tolerances. Args: path: media file to check (any format ffmpeg can read). standard: EBU_R128 (broadcast, -23 LUFS), ATSC_A85 (US TV, -24 LKFS), or BS_1770 (measurement only — verdict "measured", no gates). stream: zero-based audio stream index for multi-track files. detailed: also report max momentary / max short-term loudness (one extra ffmpeg pass). Returns: dict with: verdict (pass|fail|measured), per-metric measured/target/delta and pass booleans, failures (plain-English causes), remediation (exact corrections, e.g. "apply -2.3 LU gain"), and measurement_context (ffmpeg version, stream info). |
| list_standardsA | List the standards this tool can verdict against, with their targets, tolerances, and spec citations. |
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 2 tools
The two tools have clearly distinct purposes: one checks loudness against a standard, the other lists available standards. No overlap in functionality.
Both tool names follow a consistent verb_noun pattern: check_loudness and list_standards. The naming is predictable and clear.
With only 2 tools, the server is on the low end of the typical range. While the tools cover the core functionality, a batch processing tool or a tool to preview raw measurements would round out the set.
The server covers the main use case of loudness checking and provides standards listing. Minor gaps exist, such as batch processing or the ability to update standards, but the core workflow is complete.