Skip to main content
Glama
calebn

Podcast MCP

by calebn
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

correct_transcript_tool

Corrects one transcript word in place without altering timing; use expected text and source ID to guard against shifted indices or multi-take tracks.

Instructions

Fix the text of one transcript word without changing its timing.

Pass expected_text (the word text you read) to refuse the fix if the word at word_index changed meanwhile (for example a GUI edit shifted indices); omit to skip. source_id names the recording whose words word_index counts; it is required on a track recorded as several takes, and the refusal is word_source_required.

Input Schema

NameRequiredDescriptionDefault
new_textYes
track_idYes
source_idNo
word_indexYes
project_pathNo
expected_textNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.1.1
    • addedInput schema / properties / expected_text
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Expected Text"
+}
    • 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"
    • addedInput schema / properties / source_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Source Id"
+}
    • changedInput schema / required
      Previous value: -[
-  "project_path",
-  "track_id",
-  "word_index",
-  "new_text"
-]New value: +[
+  "track_id",
+  "word_index",
+  "new_text"
+]
  2. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the mutation is text-only (timing preserved), a stale-word refusal mechanism via expected_text, and a named failure mode (word_source_required). It omits permission/undo-history implications, but the core behavioral contract is clearly stated.

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?

Front-loads the purpose in one sentence, then layers optional-parameter semantics compactly with no filler. The backtick-heavy conditional phrasing is dense but each clause carries distinct information.

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

Completeness4/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 described. The description covers the mutation scope, the concurrency guard, and the required-source error path. It is close to complete, lacking only how the fix interacts with adjacent word indices or project_path.

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

Parameters3/5

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

Schema description coverage is 0% across 6 parameters, so the description must compensate. It explains expected_text and source_id meaningfully, but leaves track_id, word_index, new_text, and project_path (index base, format, scope) entirely to guesswork from bare titles.

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+resource+scope ('Fix the text of one transcript word') and a distinguishing constraint ('without changing its timing'), which implicitly separates it from set_word_timing_tool and correct_transcript_phrase_tool. It stops short of naming those siblings explicitly, so the differentiation relies on inference.

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

Usage Guidelines4/5

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

Gives actionable conditional guidance: pass expected_text as a concurrency guard, omit it to skip; supply source_id on multi-take tracks or the call refuses with word_source_required. It never states when to prefer this over phrase-level or find/replace siblings, so exclusions are missing.

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