Skip to main content
Glama
Sign In
mcp-freesound

mcp-freesound

by jumpifequal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get sound details

get_sound
Read-onlyIdempotent

Get full details of a single Freesound sound: technical properties (sample rate, bit depth, channels, size), license, pack, geotag, ratings, downloads, previews and waveform images.

Instructions

Get full details of a single Freesound sound: technical properties (sample rate, bit depth, channels, size), license, pack, geotag, ratings, downloads, previews and waveform images.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
sound_idYesFreesound sound ID.

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=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description's real contribution is disclosing what the response contains (technical properties, license, pack, geotag, ratings, previews, waveforms), which matters because there is no output schema. It says nothing about auth, rate limits, or error behavior for unknown IDs.

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 a concrete field enumeration and no filler. Every clause carries information about either scope or returned content.

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?

With no output schema, the enumeration of returned fields is exactly the compensating detail needed for a read-only single-resource fetch. Only the marginal gaps around missing-sound behavior and rate limits keep it from full marks.

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?

Only one parameter, sound_id, and the schema already documents it at 100% coverage with a minimum of 1, so the baseline of 3 applies. The description adds no detail about the identifier's acquisition or validity beyond what the schema states.

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 uses a specific verb ('Get full details') on a named resource ('a single Freesound sound') and enumerates the payload (technical properties, license, pack, geotag, ratings, downloads, previews, waveform). That payload list implicitly distinguishes it from get_sound_analysis and get_sound_comments, though neither sibling is named.

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?

There is no explicit when-to-use guidance, no prerequisites, and no routing to alternatives such as get_sound_analysis or find_similar_sounds. An agent must infer from the field list that this is the general-purpose detail fetch.

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