mcp-freesound

Get sound analysis

get_sound_analysis

Read-onlyIdempotent

Get audio descriptors computed by Freesound for a sound (e.g. bpm, key, loudness, brightness, pitch). Optionally restrict to specific descriptor names.

Instructions

Get audio descriptors computed by Freesound for a sound (e.g. bpm, key, loudness, brightness, pitch). Optionally restrict to specific descriptor names.

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": {
      "sound_id": "<sound_id>"
    },
    "name": "get_sound_analysis"
  }
}

Input Schema

Name	Required	Description	Default
`sound_id`	Yes	Freesound sound ID.
`descriptors`	No	Optional comma-separated descriptor names, e.g. 'bpm,tonality,loudness'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Nov 2, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered. The description adds one useful behavioral fact — descriptors are precomputed by Freesound rather than derived on demand, implying possible missing/partial values — but says nothing about error behavior for nonexistent sound IDs or result shape.

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?

Two short sentences, zero filler: the core operation and its output domain come first, with the optional filter in a subordinate trailing clause. Every phrase 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 two-parameter, read-only lookup with no output schema and full annotation coverage, the definition supplies what an agent needs: the identified resource, the data domain, and the filter mechanism. The only shortfall is that it does not describe the returned analysis object's structure, which matters somewhat given the absence of an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by naming the descriptor vocabulary (bpm, key, loudness, brightness, pitch) that the schema only hints at with one example string. This matters practically because valid descriptor names are non-obvious and the schema's example ('bpm,tonality,loudness') and the description's ('key') even differ in terminology.

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 names a specific verb and resource ('Get audio descriptors computed by Freesound for a sound') and gives concrete examples (bpm, key, loudness, brightness, pitch), which makes the tool's output domain clear. It does not explicitly contrast itself with the close sibling get_sound, so an agent must infer that this returns analysis data rather than metadata, but the wording strongly implies the distinction.

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?

Usage is only implied: it says the descriptor filter is optional, so an agent knows calling without it returns everything. There is no guidance on when to prefer this over get_sound or find_similar_sounds, and no mention that some sounds may lack analysis data — a notable gap for a Freesound-specific endpoint.

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

Deploy Server