Skip to main content
Glama
Sign In
SoundMCP

SoundMCP

by Plagnito
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

create_ambience

Generates looping 16-bit WAV ambience beds for games from a chosen kind (rain, storm, forest, ocean) and seed, using crossfades to make loop joins inaudible.

Instructions

Crée une ambiance de jeu en boucle parfaite (WAV 16 bits) : rain (pluie), storm (orage), wind (vent), forest (forêt), campfire (feu de camp), ocean (océan), river (rivière), cave (grotte), spaceship (vaisseau), cafe (café), night (nuit). Couches de bruit continu + événements stochastiques (gouttes, oiseaux, tonnerre, vagues…) ; le crossfade circulaire rend le raccord de boucle inaudible. 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_ambience"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesType d'ambiance.
monoNoExporte en mono (taille moitié).
seedNoGraine : même seed = même ambiance.
volumeNoVolume relatif (0.05 à 1).
output_dirNoDossier de sortie. Par défaut : <projet>/output.
sampling_rateNoFréquence d'échantillonnage du WAV en Hz. 22050 recommandé pour les fonds d'ambiance (taille moitié, qualité largement suffisante).
duration_secondsNoDurée de la boucle en secondes (5 à 600). Par défaut : 45-60 s selon l'ambiance. Une boucle plus longue = événements moins répétitifs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.0

TDQS

A3.5/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 burden, and it does add real behavioral detail beyond the schema: continuous noise layers plus stochastic events (drops, birds, thunder, waves) and a circular crossfade that makes the loop seam inaudible, plus seed-based determinism. It still omits operationally relevant behavior for a file-generating tool — whether existing files are overwritten, what is returned (path/filename), and that synthesis may be slow — which matters because nothing else documents it.

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?

The definition is front-loaded with the verb, output format, and loop quality, then the kind enumeration, then the technical mechanism — a sensible order for scanning. It is dense but each clause carries information (format, kinds, layers, crossfade, seed), with only the seed-determinism clause being redundant with the schema.

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 generation tool with a fully documented seven-parameter schema, no output schema, and no annotations, the description covers output format and the technical guarantees that make the result usable. The remaining gap is the return value and file-handling behavior, which is modest given how thoroughly the input schema is described.

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 one of the seven parameters is already documented, including the seed determinism, the duration/repetitiveness tradeoff, and the 22050 Hz recommendation. The description's 'Déterministe via seed' merely restates what the seed property already says, adding no syntax, defaults, or units beyond the schema; the baseline of 3 is 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 and resource ('Crée une ambiance de jeu en boucle parfaite'), names the output format (WAV 16 bits), and enumerates all eleven ambience kinds, so the agent knows exactly what is produced. It never distinguishes itself from the siblings create_music and create_sfx, leaving the agent to infer that this is the looping background-bed generator rather than a one-shot or musical one.

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: 'ambiance de jeu en boucle parfaite' signals a seamless looping background bed, which implicitly differs from a music track or a one-shot SFX, but no sentence says when to choose this over create_music or create_sfx and no exclusions or prerequisites are given. The reader must infer the routing decision from the nature of the output.

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