Skip to main content
Glama
Sign In
TranscriptionTools MCP Server

TranscriptionTools MCP Server

by MushroomFleet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

format_transcript

Convert timestamped transcripts into readable text by removing timestamps and organizing content into paragraphs and lines based on specified time gaps.

Instructions

Transforms timestamped transcripts into naturally formatted text

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input_text": "<input_text>"
    },
    "name": "format_transcript"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_textYesTimestamped transcript text or path to file
is_file_pathNoWhether input_text is a file path
line_gapNoSeconds gap for line breaks
paragraph_gapNoSeconds gap for paragraph breaks

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/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 of behavioral disclosure. It states the transformation action but lacks details on permissions, rate limits, output format, or error handling. For a tool with no annotations, this is insufficient to inform the agent about behavioral traits beyond the basic operation.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without unnecessary words. It's front-loaded and appropriately sized, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given no annotations and no output schema, the description is incomplete. It doesn't explain the return values or behavioral aspects like what 'naturally formatted text' entails. For a transformation tool with 4 parameters, more context is needed to guide the agent effectively.

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 100%, so the schema fully documents all parameters. The description doesn't add any meaning beyond what the schema provides, such as explaining how 'line_gap' and 'paragraph_gap' affect formatting. With high schema coverage, a baseline score of 3 is appropriate as the description doesn't compensate but also doesn't detract.

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 clearly states the tool's purpose: 'Transforms timestamped transcripts into naturally formatted text.' It specifies the verb ('transforms') and resource ('timestamped transcripts'), and the outcome ('naturally formatted text'). However, it doesn't differentiate from sibling tools like 'repair_text' or 'summary_text', which might also process text, so it misses full sibling distinction.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'repair_text' or 'summary_text', nor does it specify contexts or exclusions for usage. This leaves the agent without clear direction on tool selection.

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

Related Tools