Skip to main content
Glama
Sign In

PopNow

by io.github.popnow-ai
OverviewDiscussionsAdmin

Create a voiceover

create_speech

Turn text into natural speech, in many voices and languages. Priced by length in site credits with OAuth or USD with an API key.

Input Schema

NameRequiredDescriptionDefault
textYesThe exact words to read out loud.
styleNoOptional delivery: whisper, empathetic, vocal_smile, newscaster, promo_hype or deadpan.
voiceNoOptional voice name, for example Kore (default, warm female), Puck (upbeat male), Charon (deep male), Aoede (bright female), Fenrir (excited male), Leda (young female).
max_usdNoAPI key only: maximum approved USD as a decimal string with up to 9 fractional digits. Set currency to USD. Only set after the user confirms the quoted cost_usd. Never convert max_credits.
currencyNoBilling unit: USD for API keys; credits for OAuth (optional for existing OAuth clients).
max_creditsNoOAuth only: the most site credits the user agreed to spend on this. Only set it after the user confirmed a quoted price.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / properties / style / enum
      Removed value: -[
-  "whisper",
-  "empathetic",
-  "vocal_smile",
-  "newscaster",
-  "promo_hype",
-  "deadpan"
-]
  2. Changed3 schema fields changed
    • addedInput schema / properties / currency
      Added value: +{
+  "description": "Billing unit: USD for API keys; credits for OAuth (optional for existing OAuth clients).",
+  "type": "string"
+}
    • changedInput schema / properties / max_credits / description
      Previous value: -"The most credits the user agreed to spend on this. Only set it after the user confirmed a quoted price."New value: +"OAuth only: the most site credits the user agreed to spend on this. Only set it after the user confirmed a quoted price."
    • addedInput schema / properties / max_usd
      Added value: +{
+  "description": "API key only: maximum approved USD as a decimal string with up to 9 fractional digits. Set currency to USD. Only set after the user confirms the quoted cost_usd. Never convert max_credits.",
+  "type": "string"
+}
  3. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare the safety profile (not read-only, not destructive, not idempotent). The description adds genuine context beyond that: the operation is metered by text length, billed in site credits for OAuth or USD for API keys. It does not disclose latency, async/job behavior, or rate limits, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with no waste, and the core capability is front-loaded ahead of the secondary pricing detail. Nothing needs trimming or reordering.

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

Completeness3/5

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

For a six-parameter generative tool with no output schema, the description leaves a real gap: it never states what comes back (audio payload vs job id) or that generation may be asynchronous. Purpose and cost model are covered, but an agent still cannot predict the response shape.

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

Parameters3/5

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

Schema description coverage is 100%, so every parameter including voice, style, currency, max_usd and max_credits is already documented with examples and constraints. The description adds no parameter-level meaning; the pricing sentence merely echoes the credits-vs-USD distinction the schema already spells out.

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: 'Turn text into natural speech, in many voices and languages.' This is unambiguously a text-to-speech tool and is readily separable from siblings such as create_music, create_sound_effects and transcribe_audio 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 Guidelines2/5

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

No when-to-use or when-not-to-use guidance and no named alternatives. The only conditional content is billing-related ('OAuth or USD with an API key'), which is about payment mode rather than tool selection, so an agent gets no explicit routing help.

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

All PopNow 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