Skip to main content
Glama

check_engine_status

Verify if the AivisSpeech text-to-speech engine is currently operational to enable Japanese speech synthesis.

Instructions

Check if AivisSpeech engine is running

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler for the check_engine_status tool. Uses AivisSpeechClient to check if the engine is running and returns appropriate status message.
    case 'check_engine_status': {
      try {
        const isRunning = await client.isEngineRunning();
        const version = isRunning ? await client.getVersion() : null;
    
        return {
          content: [
            {
              type: 'text',
              text: isRunning 
                ? `AivisSpeech engine is running (version: ${version})`
                : 'AivisSpeech engine is not running. Please start the engine at http://127.0.0.1:10101',
            },
          ],
        };
      } catch (error) {
        return {
          content: [
            {
              type: 'text',
              text: `Error checking engine status: ${error instanceof Error ? error.message : String(error)}`,
            },
          ],
          isError: true,
        };
      }
    }
  • Supporting method isEngineRunning() in AivisSpeechClient class that checks engine status by attempting to fetch the version endpoint.
    async isEngineRunning(): Promise<boolean> {
      try {
        await this.getVersion();
        return true;
      } catch {
        return false;
      }
    }
  • src/index.ts:75-82 (registration)
    Tool registration in ListTools response when engine is NOT running (only this tool is listed).
    {
      name: 'check_engine_status',
      description: 'Check if AivisSpeech engine is running',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • src/index.ts:161-168 (registration)
    Tool registration in ListTools response when engine IS running (listed among other tools).
    {
      name: 'check_engine_status',
      description: 'Check if AivisSpeech engine is running',
      inputSchema: {
        type: 'object',
        properties: {},
      },
    },
  • Input schema for check_engine_status tool (empty object, no parameters required).
    inputSchema: {
      type: 'object',
      properties: {},
    },
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 mentions checking engine status but fails to describe what 'running' means, potential error conditions, response format, or any side effects. This leaves significant gaps for an agent to understand the tool's behavior.

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, clear sentence with no wasted words. It directly states the tool's purpose without redundancy or unnecessary elaboration, making it optimally concise and well-structured.

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?

For a tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the check returns (e.g., boolean status, detailed metrics, error messages), leaving the agent without crucial information to interpret results.

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?

The tool has zero parameters with 100% schema description coverage, so no parameter documentation is needed. The description appropriately doesn't discuss parameters, earning a high baseline score for not adding unnecessary information.

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 with a specific verb ('Check') and resource ('AivisSpeech engine'), making it immediately understandable. However, with no sibling tools mentioned, there's no opportunity to differentiate from alternatives, preventing a perfect score.

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, prerequisites, or contextual constraints. It merely states what the tool does without indicating appropriate scenarios or limitations.

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/shinshin86/mcp-simple-aivisspeech'

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