Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

check_loudness_tool

Measure LUFS and report artifact or dialogue-balance staleness without refreshing audio. Use it to verify loudness and measurement freshness in podcast projects.

Instructions

Measure LUFS and report artifact and dialogue-balance staleness without refreshing.

pass judges loudness; stale and stale_reason judge known project artifact age. balance reports per-dialogue-track measurement freshness for tracked project audio. An explicit unrelated file has stale=None.

Input Schema

NameRequiredDescriptionDefault
audio_pathNo
project_pathNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / project_path / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / project_path / default
      Added value: +null
    • removedInput schema / properties / project_path / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
-  "project_path"
-]
  2. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. 'Without refreshing' usefully signals a non-mutating read, and it names the output fields, but it omits permissions, side effects, and whether a refresh is ever triggered; with zero annotation coverage the behavioral picture is thin.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The leading sentence is front-loaded and reasonably tight, but the backtick-formatted output-field sentences read as reference notes rather than actionable guidance and are partly redundant against the output schema.

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

Completeness3/5

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

An output schema exists, so return values needn't be spelled out, but with no annotations and two undocumented optional params the definition leaves an agent unsure how to parameterize the call. Adequate but with clear gaps.

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 description coverage is 0% for two optional params (audio_path, project_path), and the description adds no meaning for either. The one hint ('an explicit unrelated file has stale=None') gestures at the audio_path case but never explains what each parameter selects or their relationship.

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?

States a specific verb and resource: 'Measure LUFS' plus staleness reporting. It is clear what the tool does, though the jargon ('artifact staleness', 'dialogue-balance') is not anchored to sibling tool names, so differentiation is only implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, nor any named alternative. At best the reader infers 'without refreshing' means this is a passive check, but the description never says in which situations an agent should pick this over a recompute/analysis tool.

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