Skip to main content
Glama
Podcast MCP
by calebn

transcript_refine_done_tool

Mark transcript refinement complete with optional notes and an expected fingerprint to reject completion if the transcript changed since review.

Instructions

Mark transcript refinement done, with optional notes.

Pass the status fingerprint you reviewed as expected_fingerprint to refuse if the transcript changed since.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "transcript_refine_done_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNo
project_pathNo
expected_fingerprintNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.4
    • addedInput schema / properties / expected_fingerprint
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Expected Fingerprint"
      +}
  2. 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"
      -]
  3. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses optimistic-concurrency behavior: the call is refused if the transcript changed since the reviewed fingerprint, which is real behavioral value. It omits idempotency, whether notes are stored or overwritten, and any permission requirements.

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?

Two short sentences with no filler, and the completion purpose is front-loaded ahead of the fingerprint caveat. The formatting with inline code markers is slightly noisy but does not cost clarity.

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 need not be explained, and the fingerprint guard is covered. But with three parameters at 0% schema coverage and no annotations, the undefined project_path and the missing contrast with waive/status siblings leave gaps for an agent deciding whether to call this.

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 coverage is 0%, so the description must compensate. It explains expected_fingerprint well, identifying it as the status fingerprint previously reviewed and the refusal semantics. However, notes gets only 'optional notes', and project_path is entirely 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?

The description gives a specific verb and resource: 'Mark transcript refinement done', with the addition of optional notes. It clearly reads as a completion signal for a refinement workflow, distinguishing it implicitly from status/waive siblings, though it never names them.

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

Usage Guidelines3/5

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

It gives condition-specific guidance for one parameter: pass the fingerprint you reviewed to refuse the call if the transcript changed. It does not state when to use this instead of transcript_refine_waive_tool or transcript_refine_status_tool, nor what precondition must hold before refinement can be marked done.

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