Skip to main content
Glama
Sign In
SoundMCP

SoundMCP

by Plagnito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_sfx

Generate ready-to-use WAV game sound effects from 32 types (action, combat, UI, nature, characters), with deterministic seed-based output for consistent variants.

Instructions

Crée un effet sonore de jeu prêt à l'emploi (WAV 16 bits, 32 types) : action (jump, coin, pickup, hit, damage, powerup, levelup), combat (explosion, laser, sword, gunShoot, bowShoot), nature (thunder, splash, whoosh), UI (click, hover, error, success, menuOpen, chestOpen, questComplete), personnages (footstep, door, heartbeat, alarm, ghost, forge, bubble, magic, teleport). Déterministe via seed.

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": {
      "kind": "<kind>"
    },
    "name": "create_sfx"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesType d'effet sonore.
monoNoExporte en mono (taille moitié).
seedNoGraine : même seed = même SFX (utile pour des variantes cohérentes).
volumeNoVolume relatif (0.05 à 1).
output_dirNoDossier de sortie. Par défaut : <projet>/output.
sampling_rateNoFréquence d'échantillonnage du WAV en Hz (22050 = taille moitié, ok pour les UI/retro).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and it does disclose two useful traits: output is a 16-bit WAV and generation is deterministic via seed. It does not say whether an existing file is overwritten, whether a file path is returned, how long generation takes, or what permissions the output directory needs.

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 that states purpose first and details after; every clause earns its place except the long parenthetical kind list, which largely restates the enum already present in the schema.

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?

For a 6-parameter file-producing tool with no output schema and no annotations, the description should clarify what is returned (path? binary? confirmation) and what happens on write collisions. It covers the input side well through the kind catalogue but leaves the result contract unstated.

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%, so every parameter including the 32-value enum, mono, seed, volume, output_dir, and sampling_rate is already documented in the schema; baseline is 3. The description only reinforces determinism via seed, adding nothing about format defaults or the mono/sampling_rate trade-offs 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 gives a specific verb and resource ('Crée un effet sonore de jeu prêt à l'emploi') and then enumerates all 32 effect kinds grouped by category, so an agent knows precisely what comes out. It does not explicitly contrast itself with create_ambience or create_music, relying instead on the term 'effet sonore' to imply a short one-shot sound rather than a loop or track.

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 implied through the catalogue of kinds (explosion, click, footstep…), which tells an agent this is the tool for discrete game SFX. There is no explicit statement of when to prefer create_ambience or create_music, nor any exclusion or prerequisite 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