Skip to main content
Glama
timjrobinson

Freesound MCP Server

by timjrobinson

get_similar_sounds

Find audio samples similar to a specific sound from Freesound.org by providing its ID, with options to filter by content descriptors and paginate results.

Instructions

Find sounds similar to a given sound

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sound_idYesThe ID of the sound to find similar sounds for
descriptors_filterNoFilter similar sounds by content descriptors
pageNoPage number (default: 1)
page_sizeNoNumber of results per page (default: 15)

Implementation Reference

  • src/index.ts:106-131 (registration)
    Tool registration in the list of tools, including name, description, and input schema definition
    {
      name: "get_similar_sounds",
      description: "Find sounds similar to a given sound",
      inputSchema: {
        type: "object",
        properties: {
          sound_id: {
            type: "number",
            description: "The ID of the sound to find similar sounds for",
          },
          descriptors_filter: {
            type: "string",
            description: "Filter similar sounds by content descriptors",
          },
          page: {
            type: "number",
            description: "Page number (default: 1)",
          },
          page_size: {
            type: "number",
            description: "Number of results per page (default: 15)",
          },
        },
        required: ["sound_id"],
      },
    },
  • MCP CallToolRequest handler for get_similar_sounds, which delegates to FreesoundClient and returns JSON response
    case "get_similar_sounds": {
      const similar = await freesoundClient.getSimilarSounds(
        args.sound_id as number,
        {
          descriptors_filter: args.descriptors_filter as string | undefined,
          page: args.page as number | undefined,
          page_size: args.page_size as number | undefined,
        }
      );
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(similar, null, 2),
          },
        ],
      };
    }
  • Core implementation of getSimilarSounds in FreesoundClient, making API call to Freesound similar sounds endpoint
    async getSimilarSounds(
      soundId: number,
      params?: SimilarSoundsParams
    ): Promise<PaginatedResults<Sound>> {
      const response = await this.axiosInstance.get(
        `/sounds/${soundId}/similar/`,
        {
          params: {
            descriptors_filter: params?.descriptors_filter,
            page: params?.page || 1,
            page_size: params?.page_size || 15,
          },
        }
      );
      return response.data;
    }
  • TypeScript interface defining parameters for getSimilarSounds
    export interface SimilarSoundsParams extends PaginationParams {
      descriptors_filter?: string;
    }
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 but offers minimal information. It implies a read operation ('Find') but doesn't detail aspects like rate limits, authentication needs, error handling, or the format of returned results. For a tool with four parameters and no output schema, 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 extremely concise—a single, direct sentence that states the core function without any fluff. It's front-loaded and wastes no words, making it easy to parse quickly. This efficiency is ideal for tool selection, though it may sacrifice detail for brevity.

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 (four parameters, no annotations, no output schema), the description is insufficiently complete. It doesn't address what 'similar' means, how results are ranked, the structure of the output, or potential limitations. Without annotations or an output schema, more context is needed to fully understand the tool's operation and results.

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 all four parameters, so the description adds no additional parameter semantics. It doesn't explain how 'sound_id' relates to similarity, what 'descriptors_filter' entails, or how pagination works in practice. The baseline score of 3 reflects adequate schema coverage without extra value from the description.

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 ('Find') and resource ('sounds similar to a given sound'), making it immediately understandable. However, it doesn't explicitly distinguish this tool from sibling tools like 'search_sounds' or 'get_sound_analysis', which might also involve sound retrieval or comparison, leaving some ambiguity about its unique role.

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. It doesn't mention scenarios where 'get_similar_sounds' is preferred over 'search_sounds' or 'get_sound_analysis', nor does it specify prerequisites or exclusions. This lack of context makes it harder for an agent to choose the right tool 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/timjrobinson/FreesoundMCPServer'

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