Skip to main content
Glama

get_all_voices

Retrieve a paginated list of available voices for text-to-speech and voice conversion tasks. Use limit and page parameters to navigate results efficiently.

Instructions

Get a paginated list of all available voices for voice conversion and TTS

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of voices per page (default: 20)
pageNoPage number for pagination (default: 0)

Implementation Reference

  • The core handler function that implements the get_all_voices tool logic. It constructs pagination parameters from input args, performs a GET request to the MusicGPT API endpoint '/getAllVoices', and returns the response data as formatted JSON text content.
    private async handleGetAllVoices(args: any) {
      const params = {
        limit: args.limit || 20,
        page: args.page || 0,
      };
    
      const response = await this.axiosInstance.get("/getAllVoices", { params });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:86-104 (registration)
    Tool registration definition in the TOOLS array. Defines the tool name, description, and input schema for pagination parameters. This is used by the MCP server's ListToolsRequestHandler to advertise the tool.
    {
      name: "get_all_voices",
      description: "Get a paginated list of all available voices for voice conversion and TTS",
      inputSchema: {
        type: "object" as const,
        properties: {
          limit: {
            type: "number",
            description: "Maximum number of voices per page (default: 20)",
            default: 20,
          },
          page: {
            type: "number",
            description: "Page number for pagination (default: 0)",
            default: 0,
          },
        },
      },
    },
  • src/index.ts:663-664 (registration)
    Dispatch registration in the CallToolRequestHandler switch statement. Routes incoming calls to the 'get_all_voices' tool to the appropriate handler method.
    case "get_all_voices":
      return await this.handleGetAllVoices(args);
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 pagination, which is useful, but lacks details on permissions, rate limits, error handling, or the return format (e.g., structure of voice data). For a read operation tool, this leaves significant gaps in understanding its 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, efficient sentence that front-loads the key action and resource. It avoids redundancy and wastes no words, making it easy to parse while conveying essential information.

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?

Given the tool's low complexity (simple read operation with 2 parameters) and high schema coverage, the description is minimally adequate. However, without annotations or an output schema, it fails to fully explain behavioral aspects like response format or limitations, leaving room for improvement in completeness.

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?

The input schema has 100% description coverage, clearly documenting both parameters with defaults. The description adds no additional semantic details beyond implying pagination, which is already covered in the schema. This meets the baseline for high schema coverage without extra value.

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 verb ('Get') and resource ('paginated list of all available voices'), specifying the purpose for voice conversion and TTS. However, it does not explicitly differentiate from the sibling tool 'search_voices', which might offer filtering capabilities, leaving some ambiguity about when to use each tool.

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 like 'search_voices' or 'text_to_speech'. It mentions pagination but does not specify scenarios or prerequisites for usage, offering only basic functional context without comparative advice.

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/pasie15/mcp-server-musicgpt'

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