Skip to main content
Glama
Sign In
mcp-freesound

mcp-freesound

by jumpifequal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List pack sounds

get_pack_sounds
Read-onlyIdempotent

Retrieve and list sounds contained in a Freesound pack by pack ID, with pagination and result limits to browse or compare audio.

Instructions

List the sounds contained in a Freesound pack.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pack_id": "<pack_id>"
    },
    "name": "get_pack_sounds"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page (1-based).
pack_idYesFreesound pack ID.
max_resultsNoNumber of results to return (1-30, default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, covering the entire safety profile. The description adds nothing beyond that, such as pagination behavior, ordering, or that the pack must exist. There is simply no behavioral context layered on top of the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler or repetition. It is efficient, though its brevity borders on under-specification rather than deliberate conciseness.

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?

No output schema exists, so the description could helpfully state what a returned sound entry contains (id, name, preview links), and it does not. Combined with rich annotations and a fully documented schema, this is adequate but leaves the agent guessing about result shape and pagination semantics.

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 pack_id, page, and max_results all documented in the schema, so the schema carries the parameter burden. The description adds no format hints (e.g., how to discover a pack_id, that max_results caps at 30), so baseline 3 applies.

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?

States a specific verb ("List") and resource ("sounds contained in a Freesound pack"), so the agent knows exactly what is returned and scoped to. It does not distinguish itself from siblings like get_pack or search_sounds, which could also surface pack-related content.

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?

No when-to-use guidance is given: nothing says to use this instead of search_sounds, or alongside get_pack (e.g., get the pack metadata first, then enumerate its sounds). The agent must infer the relationship between this tool and its siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools