Gomo Sounds

Generate a voice line

generate_voice

Generates versions (1 to 4) of a voice line created with create_voice, with its text, voice, register and emotion (spends credits: refused until the user approved the cost in the conversation, see approve_spending). A line costs its estimated seconds (characters / charsPerSecond of list_voices, at least 1 s) × creditsPerSecond × versions. Voice versions are NEVER chosen automatically, not even the first ones: the user must listen to them on the site and pick the ones that go to the game. Returns the new versions and the sound page (url): give the user that link and tell them to listen and choose there.

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": {
      "event_id": "<event_id>"
    },
    "name": "generate_voice"
  }
}

Input Schema

Name	Required	Description	Default
`event_id`	Yes	The voice line (the id create_voice returned).
`variations`	No	How many versions. Omitted: 3.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations provide only a title, so the description carries the full burden and does well: it discloses credit spend with a concrete cost formula, the approval gate and refusal behavior, that versions are never auto-selected, and what is returned (versions plus sound page URL). What it omits is failure/error behavior beyond the refusal (e.g. queueing, job status, retry after approval), which keeps it below 5.

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?

Front-loaded with purpose, then cost, then workflow, then return value — the right ordering. It is a single dense paragraph with a somewhat cramped cost formula, but no sentence is filler; only minor formatting would improve it.

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?

No output schema exists, yet the description states exactly what comes back (the new versions and the sound page URL) and what the agent must do with it. Combined with cost and approval semantics, an agent has everything needed to call and handle this tool 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: `event_id` is tied to the id returned by create_voice, and `variations` is shown to be 1–4 and to multiply the credit cost. It does not restate the default of 3 (already in the schema), which is fine.

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?

Starts with a specific verb and resource ("Generates versions (1 to 4) of a voice line") and explicitly anchors it to the sibling `create_voice`, so the agent can distinguish it from creation, listing, or approval tools. Scope (1–4 versions) is stated up front.

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?

Gives explicit prerequisites (line must exist from create_voice) and an explicit gating condition (refused until the user approved the cost, see approve_spending). It also prescribes the downstream workflow: the user must listen on the site and pick the versions, and the agent must hand over the sound page link.

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

All Gomo Sounds tools Inspect

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

Need Help?