Skip to main content
Glama
Sign In
Otohiroi MCP

Otohiroi MCP

by koyomivanp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

fetch_sound

Save a chosen sound into your project folder and record its license in CREDITS.md and sounds.license.json, with options to trim silence and match loudness.

Instructions

Save a sound into a project folder (absolute path) and record its license in CREDITS.md and sounds.license.json.

By default it trims silence from one-shot effects and matches loudness. Set FREESOUND_API_KEY to enable Freesound. May return status manual_download_needed with a page for the user to open.

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>",
      "dest": "<dest>"
    },
    "name": "fetch_sound"
  }
}

Input Schema

NameRequiredDescriptionDefault
destYes
formatNoogg
sound_idYes
normalizeNo
trim_silenceNo
allow_warningNo
loudness_lufsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses that it writes files (CREDITS.md, sounds.license.json), that it trims silence and matches loudness by default, that Freesound requires an API key, and that it can return a manual_download_needed status. It does not say whether existing destination files are overwritten, which is the main remaining gap for a mutating tool.

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?

Three short sentences, front-loaded with the primary action and side effect, with defaults and the API-key prerequisite following. Little waste, though the manual_download_needed sentence could be tied more tightly to the trigger condition.

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

Completeness2/5

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

For a 7-parameter mutating tool with no annotations, no output schema, and 0% schema description coverage, the description is under-specified. Half the parameters and the overwrite behavior remain undefined, leaving real ambiguity for correct invocation.

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

Parameters2/5

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

Schema description coverage is 0% across 7 parameters, so the description must compensate and largely does not. It clarifies dest (absolute project folder) and the trim_silence/normalize defaults, but leaves sound_id, format, allow_warning, and loudness_lufs undocumented.

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 and resource ('Save a sound into a project folder') plus the license-recording side effect, which goes beyond the opaque tool name 'fetch_sound'. It stops short of distinguishing this from siblings like get_sound or find_elsewhere, so an agent must guess which is the right entry point.

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 or when-not-to-use guidance and no named alternative among the siblings. The only conditional hint is 'Set FREESOUND_API_KEY to enable Freesound', which is a prerequisite rather than routing guidance.

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