Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Generate voiceover

generate_voice

Convert text scripts to MP3 audio URLs using selected voice models. Ideal for standalone voiceovers and narration clips.

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

A5/5.0
Behavior5/5

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

Discloses meaningful behavioral details beyond the annotations: returns an MP3 URL, invalid voice presets are refused with the engine's real list, some engines ignore presets and generate their own voice, and the reply indicates which voice actually spoke. It also exposes cost and character limits.

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?

Dense but every clause earns its place: purpose, exclusions, engine/voice behavior, refusal semantics, and cost are all packed in without repetition. The most important scoping information is front-loaded.

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?

Complete for a 3-parameter tool with no output schema and no meaningful annotations. It explains what the tool returns, what inputs mean, which siblings to use instead, failure behavior, and cost — nothing essential is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Even though schema coverage is 100%, the description adds substantial value: engine defaults, valid engine names, voice preset semantics with examples, behavior when presets are invalid, and the ≤900-character constraint. This goes well beyond the bare schema.

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 action: text-to-speech from the voice-model catalog that returns a served MP3 URL. It explicitly distinguishes itself from render_ad, generate_video, and change_voice, so an agent can tell it apart from those siblings without opening their schemas.

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 guidance: use for standalone voiceover/narration clips, NOT for adding audio to video, and names the alternatives (render_ad, generate_video, change_voice). It also clarifies engine/voice selection behavior and the 900-character limit.

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