Skip to main content
Glama
Sign In
mcp-freesound

mcp-freesound

by jumpifequal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List user packs

get_user_packs
Read-onlyIdempotent

List the sound packs a Freesound user has created, with paging and result limits, to explore their collections by username.

Instructions

List the packs (collections of sounds) created by a Freesound user.

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": {
      "username": "<username>"
    },
    "name": "get_user_packs"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page (1-based).
usernameYesFreesound username.
max_resultsNoNumber of results to return (1-30, default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds only the semantic definition of a pack; it does not mention whether private packs are visible, what pagination behavior looks like, or any rate-limit context implied by openWorldHint.

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?

A single front-loaded sentence with no filler, hedging, or repeated information. Every element (verb, resource, parenthetical definition, scope) earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter read tool with full schema coverage and complete annotations, the description is nearly sufficient. The only gap is the absence of an output schema combined with no mention of what a pack record contains (id, name, sound count) or how pagination metadata is returned.

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 page, username, and max_results all documented including default and min/max bounds, so the schema carries the burden. The description adds no parameter-level meaning beyond noting the username is a Freesound user, which is the baseline 3 case.

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 and resource ("List the packs ... created by a Freesound user") and parenthetically clarifies that packs are collections of sounds, which is useful domain grounding. It does not, however, distinguish itself from siblings like get_pack or get_user_sounds, so the agent must infer the boundary.

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 offers no explicit when-to-use guidance, no prerequisites, and no alternatives. It never mentions that get_pack retrieves a single pack or that get_user_sounds lists the user's individual sounds, so routing between these siblings is left entirely to the agent.

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