Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Generate voiceover

generate_voice

Turn a script into a standalone voiceover or narration clip: choose an engine and voice, synthesize the text, and get a served MP3 URL.

Instructions

RAW text-to-speech from the voice-model catalog: speak a script in a chosen voice and return the served MP3 URL. For a standalone voiceover / narration clip — NOT for adding audio to a video (render_ad and generate_video voice their own spots; change_voice re-voices a finished clip). engine picks the voice model (default 'seed-audio'; also 'eleven-v3', 'minimax-speech', 'kokoro'); voice is a preset name from that engine (see hermoso_capabilities -> voice engines) — a name that engine does not have is REFUSED for free with its real list, and a few engines generate their own voice and take no preset at all (the reply says which voice actually spoke). Paid (a couple of credits by length; ≤900 characters).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesthe script to speak (≤900 characters)
voiceNoa voice preset from the chosen engine (e.g. 'Aria'/'George' on eleven-v3, 'stokie_en' on seed-audio) — omit for the engine default
engineNovoice-engine id: 'seed-audio' (default), 'eleven-v3', 'minimax-speech', or 'kokoro' — listed in hermoso_capabilities

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "audio": {
-      "description": "the served absolute URL of the MP3 voice clip",
-      "type": "string"
-    },
-    "creditsUsed": {
-      "description": "credits billed for this clip",
-      "type": "number"
-    },
-    "model": {
-      "description": "the voice engine label",
-      "type": "string"
-    },
-    "voice": {
-      "description": "the voice preset used",
-      "type": "string"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only state readOnly=false, idempotent=false, openWorld=true, destructive=false. The description goes well beyond: it discloses cost ('a couple of credits by length'), a hard input limit ('≤900 characters'), graceful failure semantics ('a name that engine does not have is REFUSED for free with its real list'), and the surprising case where some engines ignore the preset and report which voice actually spoke.

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 purpose and the primary exclusion are front-loaded, and every clause carries information (limits, cost, error behavior, defaults). It is dense to the point of being a wall of nested parentheticals, which costs it the top score, but no sentence is filler.

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?

With no output schema, the description still states the return value ('the served MP3 URL'). Combined with cost, length cap, default engine, voice-selection rules, and the pointer to hermoso_capabilities for valid voices, an agent has everything needed to call this 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 beyond the schema: the engine default ('seed-audio'), the cross-parameter constraint that a voice must belong to the chosen engine, and the case where some engines take no preset at all. It stops short of documenting the output shape per parameter, but the added semantics are substantive.

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+resource ('RAW text-to-speech from the voice-model catalog: speak a script in a chosen voice and return the served MP3 URL') and immediately distinguishes itself from siblings by naming render_ad, generate_video, and change_voice as different. An agent can identify the tool's job without opening the schema.

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?

Explicitly gives the when ('standalone voiceover / narration clip') and the when-not ('NOT for adding audio to a video'), then names the three alternatives and why they differ. This is textbook routing guidance with no inference required.

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