Skip to main content
Glama

APEX AI, LLM, Embeddings, OCR & Media

Text to speech

text_to_speech
Read-onlyIdempotent

Synthesize spoken English MP3 audio (base64 audio_base64) from text (3-1000 chars) via Deepgram Aura-2. $0.004 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "text": "<text>"
    },
    "name": "text_to_speech"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYestext to synthesize into speech (3-1000 chars)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.
speakerNovoice speaker: luna (default), asteria, orion, stella, zeus, athena, hera, apollo, or helios

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing pricing, the x402 handshake, the accepted currencies/chains, and that the purchase settles inside the call. The annotations declare readOnlyHint=true while the description describes a paid settlement, which is a mild tension worth noting, but the tool itself does not mutate caller-owned resources, so it is not a direct contradiction.

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 dense sentences with zero filler, ordered output-then-price-then-protocol so the most decision-relevant facts lead. The first sentence is somewhat information-packed (format, field name, length limit, provider in one clause), but nothing is redundant.

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?

With no output schema, the description usefully names the return field and audio format, and it fully covers the payment mechanics that make this tool risky to call blindly. Remaining gaps are minor: no mention of failure behavior for an invalid or expired payment payload, or of latency/size expectations for the returned base64.

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 already 100%, so the baseline is 3, and the description adds real meaning on top: `payment` is not just a signed payload but the second step of a terms-then-pay flow. The `speaker` voice list is left entirely to the schema, which is acceptable since it is fully documented there.

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 ('Synthesize spoken English MP3 audio ... from text'), pins the output field (base64 audio_base64), the input constraint (3-1000 chars) and the backend (Deepgram Aura-2). Nothing else in the sibling list does text-to-speech, so the tool is unambiguous at a glance.

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 an explicit two-call protocol: call once without `payment` to retrieve terms, sign them with your own wallet, then call again with `payment`. It also states the cost ($0.004 per call) and accepted payment rails up front, so an agent knows exactly what sequence to execute before spending money.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.