Skip to main content
Glama

Text-to-Speech Payment Quote

tts_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/tts (standard $0.03, neural $0.08, neural-short $0.03; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: POST {text, voice?, format?} with ?tier=standard (up to 3000 characters), neural (up to 2500) or neural-short (up to 1000). Plain text only; stock voices only, no voice cloning; mp3 by default or ogg_vorbis. Machine-generated audio: no impersonation, no speech-model training, no competing text-to-speech service; keep any watermark or metadata.. Horizon Pulse text-to-speech: POST JSON {text, voice?, format?}; returns audio (base64; mp3 by default, or ogg_vorbis) from a stock synthetic voice. Stock voices only; no voice cloning. tier=standard ($0.03, up to 3000 characters), tier=neural ($0.08, up to 2500 characters) or tier=neural-short ($0.03, up to 1000 characters); each tier's cap is set by the tier you pay for. Plain text only (no SSML); characters are Unicode code points. Over

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tts_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations, the description adds pricing details, payment protocol, tier character limits, content restrictions, and the important fact that this tool never performs the check or pays. These are useful behavioral disclosures, though repetition and the incomplete final sentence reduce precision.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

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

The description is heavily repetitive, restating the endpoint, tiers, pricing, voice constraints, and output format multiple times. It also ends with an incomplete sentence fragment ('Over'), and the duplicated blocks make it harder to scan despite the useful front-loaded first sentence.

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?

For a zero-parameter quote tool with rich annotations and no output schema, the description supplies substantial context: price per tier, USDC on Base, x402 payment flow, limits, and content restrictions. It still does not specify the exact response shape for the quote itself, which is the main remaining gap.

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?

The tool has zero input parameters, so the schema is trivially complete and the baseline is 4. The description mentions downstream API payload fields like text, voice, and format, but frames them as part of the separate HTTP payment step rather than as inputs to this tool.

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?

The description clearly states the tool returns payment terms for the Horizon Pulse TTS endpoint and explicitly distinguishes that it does not run the check or pay. It names the resource and pricing tiers, though the duplicated and trailing text slightly muddies the core purpose.

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

Usage Guidelines3/5

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

It implies the tool is used to obtain a payment quote before paying separately over HTTP, and it clarifies the tool itself does not execute or pay. However, it gives no explicit when-to-use guidance relative to sibling quote tools and no when-not-to-use conditions.

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.