Skip to main content
Glama
Sign In

Simpler.Asia

by asia.simpler
OverviewDiscussionsAdmin

studio.generate_voiceover

Generate narration audio from a script. voice_tier is the REAL choice the user makes: 'standard' ($0.015/1K chars at provider cost) vs 'premium' ($0.06/1K chars at provider cost) — quote both prices when proposing; never pick silently. Returns an audio asset id.

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": {
      "project_id": "<project_id>",
      "script": "<script>",
      "voice_tier": "<voice_tier>"
    },
    "name": "studio.generate_voiceover"
  }
}

Input Schema

NameRequiredDescriptionDefault
voiceNoProvider voice id/name (optional).
scriptYesThe narration text (max 5000 chars).
project_idYesThe studio project (vp_…) this tool acts on.
voice_tierYesREQUIRED — the user's explicit price-visible choice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description usefully adds that this incurs provider cost at per-1K-character rates and returns an audio asset id. It does not mention credit-account requirements, per-project locking, or expected generation latency, which keeps it from a 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?

Three sentences, front-loaded with the effect and immediately followed by the decision the agent must escalate. The pricing parentheticals are dense but carry information the agent is told to act on, so they earn their place.

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?

Covers what it does, the decisive parameter with cost implications, and the return value (audio asset id), which is needed since there is no output schema. It omits practical constraints like the 5000-char script limit and generation latency, both of which are relevant to a real invocation.

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 baseline is 3, but the description adds genuine meaning to voice_tier that the schema cannot: the concrete price difference between standard and premium and the requirement to surface both. The optional 'voice' parameter gets no narrative treatment beyond the schema.

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?

States a specific verb and resource: 'Generate narration audio from a script', which is clearly distinct from studio.generate_music and studio.transcribe in the sibling list. The distinction is implicit in the resource name rather than stated, so it stops short of a 5.

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

Usage Guidelines4/5

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

Gives an explicit invocation rule for the decisive parameter: quote both prices when proposing and 'never pick silently'. That is real guidance about how to call it, though it says nothing about when to use this versus generating music or transcribing existing audio.

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

All Simpler.Asia 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