Skip to main content
Glama
Mateobustamante1

orchard-mcp

by Mateobustamante1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

transcribe_url

Transcribe audio from a YouTube link or direct audio file URL. Auto-detects language and supports speaker diarization to label who said what.

Instructions

Transcribe audio from a URL (YouTube link or a direct audio file URL) with Orchard. Language auto-detected when omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesYouTube URL or direct audio URL.
promptNoBias the transcriber toward domain terms, names or acronyms.
diarizeNoLabel who said what (speaker diarization).
languageNoISO code like 'es', 'pt', 'en'. Leave empty to auto-detect.
num_speakersNoExact number of speakers, if known. Improves diarization on phone calls.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

No annotations provided, so description must carry transparency. It mentions language auto-detection but does not specify side effects, output format, or rate limits. No contradictions.

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?

One concise sentence front-loaded with the action. No unnecessary details.

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?

The description is sufficient for a simple tool but lacks any mention of the return value or error conditions. Could be more complete with output expectations.

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 descriptions are comprehensive (100% coverage), so description adds little extra. The description does not clarify parameter relationships beyond what schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb 'Transcribe' and resource 'audio from a URL' (YouTube or direct audio). Clearly distinguishes from sibling tools like transcribe_file which presumably handles files.

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?

Implies usage for URL-based audio, but does not explicitly mention alternatives like transcribe_file for files. Lacks explicit when-not to use.

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