SiteCheck

Convert text to speech in 6 languages

tts

Read-only

Text-to-speech as base64 audio. Default: MeloTTS WAV, up to 2,000 chars, in English, Spanish, French, Chinese, Japanese or Korean, $0.002. quality "high": Deepgram Aura-2 natural English voices as MP3, up to 500 chars, $0.02. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

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": "tts"
  }
}

Input Schema

Name	Required	Description
`lang`	No	en, es, fr, zh, ja or ko (default en)
`text`	Yes	Up to 2000 chars (500 with quality high)
`voice`	No	quality high only: luna, asteria, athena, helena, hera, aurora, orion, apollo, arcas, atlas, hermes, zeus, draco, odysseus
`quality`	No	standard (default, $0.002) or high (Aura-2 English, $0.02)

Output Schema

Name	Required	Description	Default
`lang`	No
`mime`	No
`model`	No
`quality`	No
`audio_base64`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 16, 2026

addedInput schema / properties / lang

Added value: +{
+  "description": "en, es, fr, zh, ja or ko (default en)",
+  "type": "string"
+}

addedInput schema / properties / quality

Added value: +{
+  "description": "standard (default, $0.002) or high (Aura-2 English, $0.02)",
+  "type": "string"
+}

changedInput schema / properties / text / description

Previous value: -"Up to 1000 chars"New value: +"Up to 2000 chars (500 with quality high)"

changedInput schema / properties / voice / description

Previous value: -"luna, asteria, athena, helena, hera, aurora, orion, apollo, arcas, atlas, hermes, zeus, draco, odysseus"New value: +"quality high only: luna, asteria, athena, helena, hera, aurora, orion, apollo, arcas, atlas, hermes, zeus, draco, odysseus"

addedOutput schema / properties / lang
```
Added value: +{}
```
addedOutput schema / properties / quality
```
Added value: +{}
```
removedOutput schema / properties / voice
```
Removed value: -{}
```

Changed1 schema field changedOct 14, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "audio_base64": {},
+    "mime": {},
+    "model": {},
+    "voice": {}
+  },
+  "type": "object"
+}

First observedOct 8, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only say readOnly and openWorld; the description adds substantial behavior beyond that: base64 audio return format, per-engine character ceilings, model providers, and a full payment model (x402, USDC on Base/Solana/Arc, charged only on success). The 'failed calls are not charged' guarantee is exactly the kind of cost/risk context an agent needs before invoking a paid tool.

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?

Front-loaded with the core behavior and structured as default-mode, then high-mode, then pricing. The price is effectively stated twice ($0.002 appears both in the default clause and again in the final pricing sentence), which is minor redundancy in an otherwise dense, waste-free definition.

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?

Output schema exists, so the return payload needn't be explained, and the description still names base64 audio. Combined with limits, language coverage, mode tradeoffs, and the micropayment mechanism, an agent has everything needed to call this paid tool correctly on the first attempt.

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 lang, text, voice, and quality are already documented in structured data. The description adds the mapping of quality levels to concrete engines and output formats (WAV vs MP3) and enumerates the languages in prose, but adds no syntax or constraint detail beyond the 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 verb and resource ('Text-to-speech as base64 audio') and immediately differentiates the two operating modes: default MeloTTS WAV in six languages vs. quality "high" Deepgram Aura-2 MP3. An agent can tell exactly what it gets back and under which mode 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 Guidelines4/5

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

Gives clear guidance for choosing between the standard and high-quality paths (high is English-only, capped at 500 chars, 10x the price), which is the real decision an agent faces here. It stops short of naming sibling alternatives such as transcribe or translate, but the mode-selection guidance is concrete.

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

All SiteCheck tools Inspect

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.