Skip to main content
Glama
timjrobinson

Freesound MCP Server

by timjrobinson

get_pack

Retrieve detailed information about a specific sound pack from Freesound.org using its unique pack ID.

Instructions

Get information about a sound pack

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pack_idYesThe ID of the pack

Implementation Reference

  • Handler logic for the 'get_pack' tool: calls FreesoundClient.getPack with pack_id argument and returns the pack data as JSON text.
    case "get_pack": {
      const pack = await freesoundClient.getPack(args.pack_id as number);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(pack, null, 2),
          },
        ],
      };
    }
  • src/index.ts:168-181 (registration)
    Registration of the 'get_pack' tool in the ListTools response, including name, description, and input schema requiring 'pack_id'.
    {
      name: "get_pack",
      description: "Get information about a sound pack",
      inputSchema: {
        type: "object",
        properties: {
          pack_id: {
            type: "number",
            description: "The ID of the pack",
          },
        },
        required: ["pack_id"],
      },
    },
  • Core implementation of getPack in FreesoundClient: makes API GET request to /packs/{packId}/ and returns the Pack data.
    async getPack(packId: number): Promise<Pack> {
      const response = await this.axiosInstance.get(`/packs/${packId}/`);
      return response.data;
    }
  • TypeScript interface defining the structure of a Pack object returned by getPack.
    export interface Pack {
      id: number;
      url: string;
      description: string;
      created: string;
      name: string;
      username: string;
      num_sounds: number;
      sounds: string;
      num_downloads: number;
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states 'Get information' which implies a read operation, but doesn't disclose behavioral traits like authentication needs, rate limits, error conditions, or what specific information is returned (e.g., metadata, details).

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 zero waste. It's appropriately sized and front-loaded, clearly stating the tool's purpose without unnecessary elaboration.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what information is returned (e.g., pack metadata, sounds list), error handling, or usage context, leaving significant gaps for a tool with one required parameter.

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?

Schema description coverage is 100%, with the parameter 'pack_id' documented as 'The ID of the pack'. The description adds no additional meaning beyond this, so it meets the baseline of 3 where the schema does the heavy lifting.

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 'information about a sound pack', making the purpose understandable. However, it doesn't differentiate from sibling tools like 'get_pack_sounds' or 'get_sound', which might retrieve related but different information.

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. With siblings like 'get_pack_sounds' (likely for sounds within a pack) and 'get_sound' (for individual sounds), there's no indication of context or exclusions for this tool.

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