Skip to main content
Glama

kobold_transcribe

Convert audio files to text using Whisper speech recognition technology for transcription and analysis.

Instructions

Transcribe audio using Whisper

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
apiUrlNohttp://localhost:5001
audioYes
languageNo

Implementation Reference

  • Handler logic that dispatches kobold_transcribe by validating input with TranscribeSchema, forwarding POST request to KoboldAI /api/extra/transcribe endpoint, and returning the response.
    if (postEndpoints[name]) {
        const { endpoint, schema } = postEndpoints[name];
        const parsed = schema.safeParse(args);
        if (!parsed.success) {
            throw new Error(`Invalid arguments: ${parsed.error}`);
        }
    
        const result = await makeRequest(`${apiUrl}${endpoint}`, 'POST', requestData);
        return {
            content: [{ type: "text", text: JSON.stringify(result, null, 2) }],
            isError: false,
        };
    }
  • Zod schema defining input for kobold_transcribe tool: optional apiUrl (from BaseConfigSchema), required audio string, optional language.
    const TranscribeSchema = BaseConfigSchema.extend({
        audio: z.string(),
        language: z.string().optional(),
    });
  • src/index.ts:208-212 (registration)
    Registers kobold_transcribe tool in ListTools response with name, description, and inputSchema.
    {
        name: "kobold_transcribe",
        description: "Transcribe audio using Whisper",
        inputSchema: zodToJsonSchema(TranscribeSchema),
    },
  • src/index.ts:335-335 (registration)
    Maps kobold_transcribe tool name to its KoboldAI endpoint and schema for dispatch in CallTool handler.
    kobold_transcribe: { endpoint: '/api/extra/transcribe', schema: TranscribeSchema },
  • Helper function used by all POST tool handlers, including kobold_transcribe, to make HTTP requests to KoboldAI API.
    async function makeRequest(url: string, method = 'GET', body: Record<string, unknown> | null = null) {
        const options: RequestInit = {
            method,
            headers: body ? { 'Content-Type': 'application/json' } : undefined,
        };
        
        if (body && method !== 'GET') {
            options.body = JSON.stringify(body);
        }
    
        const response = await fetch(url, options);
        if (!response.ok) {
            throw new Error(`KoboldAI API error: ${response.statusText}`);
        }
        
        return response.json();
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the core function but omits critical details: it doesn't specify if this is a read-only operation, potential rate limits, authentication needs, or what happens with invalid inputs. For a tool with 3 parameters and no annotation coverage, this is a significant gap in transparency.

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 extremely concise at three words, front-loaded with the core action. There is zero waste or redundancy, making it efficient for quick scanning, though this brevity contributes to gaps in other dimensions.

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 the tool's complexity (3 parameters, no output schema, no annotations), the description is incomplete. It doesn't cover parameter meanings, behavioral traits, or usage context. For a transcription tool that likely involves audio processing and API interaction, more detail is needed to guide effective use.

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?

Schema description coverage is 0%, so the description must compensate but adds no parameter information. It doesn't explain what 'audio' expects (e.g., file path, base64 data, URL), what 'apiUrl' is for, or how 'language' affects transcription. With 3 undocumented parameters, the description fails to provide necessary semantics beyond the bare schema.

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 'Transcribe audio using Whisper' clearly states the verb ('transcribe') and resource ('audio'), specifying the technology used ('Whisper'). It distinguishes from siblings like 'kobold_tts' (text-to-speech) and 'kobold_chat' (chat), but doesn't explicitly differentiate from other audio-related tools like 'kobold_interrogate' (which might analyze audio differently).

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 guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites, limitations, or scenarios where other tools (e.g., 'kobold_interrogate' for audio analysis or 'kobold_tts' for speech generation) might be more appropriate. The description lacks context for selection among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PhialsBasement/KoboldCPP-MCP-Server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server