Skip to main content
Glama

Ludo AI Game Assets

by ai.ludo
OverviewDiscussionsAdmin

createSoundEffect

Produce a short sound effect (SFX) from a text description, such as "laser gun firing" or "footsteps on gravel". The job result is a single audio result containing a URL. The description field is required, duration is capped at 10 seconds (0 means auto-pick based on the description), and you may set loop to true for a seamlessly looping effect. Credits are held when the job is accepted and refunded if it fails or is cancelled. Use this for short, discrete sounds; use createAmbiance for a continuous looping background soundscape, createMusic for musical pieces, and createAudioTransform to remix an existing audio sample. Pass an optional request_id to tag the result so you can locate it later via listGenerations (type audio). Async generation job: returns {id, status} - poll getApiJob (job and credit contract: see the server instructions).

Credits: This endpoint consumes 2 credits per call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestBodyYesPayload for generating a sound effect from a text description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / requestBody / properties / request_id / description
      Previous value: -"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable with the results endpoint."New value: +"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable as the request_id filter of listGenerations."
  2. Changed6 schema fields changed
    • removedInput schema / properties / requestBody / properties / augment_prompt / default
      Removed value: -true
    • changedInput schema / properties / requestBody / properties / augment_prompt / description
      Previous value: -"Augment the prompt behind the scenes. Disable to have more control."New value: +"Augment the prompt behind the scenes. Disable to have more control. Default: true."
    • removedInput schema / properties / requestBody / properties / duration / default
      Removed value: -0
    • changedInput schema / properties / requestBody / properties / duration / description
      Previous value: -"Duration in seconds. Use 0 for automatic duration based on the description."New value: +"Duration in seconds. Use 0 for automatic duration based on the description. Default: 0."
    • removedInput schema / properties / requestBody / properties / loop / default
      Removed value: -false
    • changedInput schema / properties / requestBody / properties / loop / description
      Previous value: -"Generate a sound effect that loops seamlessly."New value: +"Generate a sound effect that loops seamlessly. Default: false."
  3. Changed1 schema field changed
    • changedInput schema / properties / requestBody / properties / request_id / description
      Previous value: -"Optional client-provided identifier for this request. Use this to retrieve results later via the results endpoint."New value: +"Optional client-provided identifier, unique per request. Re-sending the same request_id returns the existing job instead of generating again. Also usable with the results endpoint."
  4. Changed1 schema field changed
    • addedInput schema / properties / requestBody / properties / loop
      Added value: +{
+  "default": false,
+  "description": "Generate a sound effect that loops seamlessly.",
+  "example": false,
+  "type": "boolean"
+}
  5. Changed1 schema field changed
    • addedInput schema / properties / requestBody / properties / request_id
      Added value: +{
+  "description": "Optional client-provided identifier for this request. Use this to retrieve results later via the results endpoint.",
+  "type": "string"
+}
  6. Added

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: credit hold/refund behavior, 2-credit cost, async job returning {id, status}, polling via getApiJob, and a single audio result containing a URL. These behavioral details go well beyond what the schema alone provides.

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?

The description is long but tightly organized: purpose first, then concrete constraints, sibling routing, async contract, and credit cost. Every sentence carries operational value and none merely repeat the tool name or schema verbatim.

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

Completeness5/5

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

Despite having no output schema and no annotations, the description supplies the essential execution context: async status shape, polling instruction, result form, credit contract, and when to choose sibling tools. An agent has enough information to invoke the tool and handle the follow-up correctly.

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?

Input schema coverage is 100%, so the baseline is 3. The description adds useful cross-tool and behavioral semantics: duration 0 means auto-pick, loop creates a seamlessly looping effect, and request_id lets the agent locate results via listGenerations. It does not mention augment_prompt, but the schema fully documents that parameter, so the gap is minor.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Produce a short sound effect (SFX) from a text description', with concrete examples like 'laser gun firing'. It also explicitly distinguishes itself from createAmbiance, createMusic, and createAudioTransform, making sibling differentiation clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: 'Use this for short, discrete sounds; use createAmbiance for a continuous looping background soundscape, createMusic for musical pieces, and createAudioTransform to remix an existing audio sample.' It also tells the agent to poll getApiJob for the async result, so the follow-up action is specified rather than implied.

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

All Ludo AI Game Assets toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources