Skip to main content
Glama

check_config

Verify that whisper-cli.exe, model, and FFmpeg are correctly installed and accessible. Run this tool first if any transcription issues occur.

Instructions

Verify whisper-cli.exe, model, and FFmpeg are all available. Run this first if anything fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the check_config tool: validates whisper-cli, model file, and FFmpeg existence, then returns a status report.
    if (name === "check_config") {
      const error = validatePaths();
      if (error) return { content: [{ type: "text", text: `❌ Configuration error:\n\n${error}` }], isError: true };
    
      let ffmpegStatus = "✅ Found";
      try { await execFileAsync(FFMPEG_PATH, ["-version"], { windowsHide: true }); }
      catch { ffmpegStatus = "⚠️  Not found — video/non-MP3 formats require FFmpeg in PATH"; }
    
      return {
        content: [{
          type: "text",
          text:
            `✅ Configuration looks good!\n\n` +
            `whisper-cli: ${WHISPER_CLI_PATH}\n` +
            `Model:       ${WHISPER_MODEL}\n` +
            `Threads:     ${WHISPER_THREADS} of ${SYSTEM_THREADS} logical cores\n` +
            `FFmpeg:      ${ffmpegStatus}\n\n` +
            `Optional env vars: WHISPER_THREADS, FFMPEG_PATH`,
        }],
      };
    }
  • Registration entry for check_config: name, description, and empty input schema (no parameters required).
    {
      name: "check_config",
      description: "Verify whisper-cli.exe, model, and FFmpeg are all available. Run this first if anything fails.",
      inputSchema: { type: "object", properties: {} },
  • src/index.ts:1009-1013 (registration)
    check_config is registered in the ListToolsRequestSchema handler alongside all other tools.
    {
      name: "check_config",
      description: "Verify whisper-cli.exe, model, and FFmpeg are all available. Run this first if anything fails.",
      inputSchema: { type: "object", properties: {} },
    },
  • The validatePaths() helper function called by the check_config handler to verify whisper-cli and model file existence.
    function validatePaths(): string | null {
      if (!existsSync(WHISPER_CLI_PATH))
        return `whisper-cli.exe not found at: ${WHISPER_CLI_PATH}\nCheck WHISPER_CLI_PATH in claude_desktop_config.json`;
      if (!existsSync(WHISPER_MODEL))
        return `Whisper model not found at: ${WHISPER_MODEL}\nCheck WHISPER_MODEL in claude_desktop_config.json`;
      return null;
    }
Behavior3/5

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

With no annotations, the description carries full burden. It discloses it is a verification tool with no destructive effects, but lacks details on return format, error behavior, or what happens if checks fail.

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?

Two sentences, front-loaded with purpose and usage. Every word adds value, no redundancy.

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?

For a simple zero-param tool with no output schema, the description covers essentials: what it checks and when to use. Could mention if it returns a boolean or throws on failure, but sufficient.

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

Parameters4/5

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

Zero parameters, so baseline is 4. No additional parameter info needed since none exist.

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?

Description clearly states it verifies availability of three specific components: whisper-cli.exe, model, and FFmpeg. It also provides a specific use case ('Run this first if anything fails'), distinguishing it from related tools like check_system.

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?

Provides explicit guidance to run first when failures occur. While it doesn't state when not to use it or compare to alternatives like check_system, the context is clear enough for basic usage.

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/eviscerations/whisper-windows-mcp'

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