Skip to main content
Glama

search_voices

Find specific voices by name to use for audio generation and voice conversion tasks within the MusicGPT audio processing system.

Instructions

Search for voices by name

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
voice_nameYesName of the voice to search for

Implementation Reference

  • The handler function that executes the search_voices tool. Validates input, calls the MusicGPT API endpoint /searchVoices with voice_name parameter, and returns the response as JSON text.
    private async handleSearchVoices(args: any) {
      if (!args.voice_name) {
        throw new McpError(ErrorCode.InvalidParams, "voice_name is required");
      }
    
      const response = await this.axiosInstance.get("/searchVoices", {
        params: { voice_name: args.voice_name },
      });
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(response.data, null, 2),
          },
        ],
      };
    }
  • Tool schema definition in the TOOLS array, used for tool listing and validation. Specifies name, description, and input schema requiring 'voice_name' string.
    {
      name: "search_voices",
      description: "Search for voices by name",
      inputSchema: {
        type: "object" as const,
        properties: {
          voice_name: {
            type: "string",
            description: "Name of the voice to search for",
          },
        },
        required: ["voice_name"],
      },
    },
  • src/index.ts:665-666 (registration)
    Tool name registration in the CallToolRequestSchema switch statement, dispatching calls to the handleSearchVoices handler.
    case "search_voices":
      return await this.handleSearchVoices(args);
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the basic action but fails to describe key traits: whether this is a read-only operation, if it requires authentication, what the return format looks like (e.g., list of voice objects with IDs), or any rate limits. For a search tool with zero annotation coverage, 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 with no wasted words. It is front-loaded with the core purpose, making it easy to parse quickly. Every word earns its place by conveying essential information without redundancy.

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 complexity of a search operation with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., voice details, IDs), how results are structured, or any behavioral nuances like pagination or error handling. For a tool that likely returns a list of voices, more context is needed to use it effectively.

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 schema description coverage is 100%, with the single parameter 'voice_name' fully documented in the schema. The description adds no additional meaning beyond what the schema provides, such as explaining search semantics (e.g., partial matches, case sensitivity). Given the high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 action ('Search for') and resource ('voices'), with the qualifier 'by name' adding specificity. However, it doesn't distinguish this tool from the sibling 'get_all_voices', which appears to be a related listing tool, leaving some ambiguity about when to use one versus the other.

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 'get_all_voices' or other audio-related tools. It lacks context about prerequisites, such as whether a voice library must be loaded or if this searches a global database, and offers no explicit when-not-to-use 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