Skip to main content
Glama
Sign In
mcp-freesound

mcp-freesound

by jumpifequal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

List user sounds

get_user_sounds
Read-onlyIdempotent

Retrieve sounds uploaded by a specified Freesound user, with page and result-count controls for browsing or auditing a creator's audio catalog.

Instructions

List the sounds uploaded 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_sounds"
  }
}

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.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that: it says nothing about pagination behaviour, whether results are capped (the schema caps at 30), ordering, or what a missing user yields. For a list operation the agent gets no behavioural context it couldn't infer from the name.

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 zero filler, correctly sized for a three-parameter read tool. It is efficient but so terse that it has no room to carry the discriminating detail a sibling-routing agent would want.

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?

This is a simple read-only list tool with full schema coverage and no output schema, so the description does not need to explain return values. Still, it omits the one thing that would help an agent choose between it and the other listing/searching siblings, leaving it minimally adequate rather than complete.

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 each documented with defaults and bounds, so the description need not repeat them. It adds no extra meaning such as sort order or what page does at the end of a result set, leaving the baseline 3 appropriate.

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 gives a specific verb-plus-resource ("List the sounds uploaded by") scoped to a Freesound user, which an agent can immediately map to the required username parameter. It stops short of naming how it differs from close siblings like search_sounds or get_pack_sounds, so it is clear but not fully differentiated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage context is implied by "uploaded by a Freesound user" – an agent can infer this is the tool for enumerating a user's catalogue rather than searching or fetching a single sound. However, it never states when to prefer it over search_sounds or get_pack_sounds, and gives no prerequisites or exclusions.

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