Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pipeline_get_config_tool

Retrieve effective pipeline configuration, step metadata, and parameter schema for a podcast project, including resolved forced-alignment status for precise word boundaries.

Instructions

Return effective pipeline config, step metadata, and param schema (same as GUI).

forced_alignment is the resolved Precise word boundaries state (enabled, requested, installed, blocked, reason): on by default when the word aligner is downloaded, unavailable until then (#780).

Input Schema

NameRequiredDescriptionDefault
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

B3/5.0
Behavior3/5

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

No annotations, so the description carries the burden. It implies a safe read ('Return') and helpfully documents the forced_alignment state model (enabled/requested/installed/blocked/reason) and its default behavior. It does not, however, describe permissions, side effects, or the overall structure of what else is returned beyond what the output schema covers.

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?

The core purpose is front-loaded in the first sentence, with the forced_alignment detail as supporting context. It is appropriately sized, though the parenthetical enum listing is slightly heavy for a single returned field.

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 structure needn't be restated, and the description usefully elaborates one returned field. The gap is the undocumented input parameter and the absence of any guidance on when the tool should be invoked relative to the pipeline siblings.

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?

The single parameter project_path has 0% schema description coverage, and the description never explains it or its optional/default-null semantics. A baseline of 4 would apply only with zero parameters; here the one parameter is undocumented in both schema and description.

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: 'Return effective pipeline config, step metadata, and param schema.' The read-oriented framing clearly separates it from pipeline_set_config_tool. However, it never names or contrasts with its nearest siblings (pipeline_set_config_tool, pipeline_run), so the distinction is inferable rather than explicit.

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?

No when-to-use or when-not-to-use guidance. It does not say to call this before pipeline_run or pipeline_analyze_tool, nor whether it requires a prior session or project. 'Same as GUI' is context, not a usage condition.

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