APICK

TTS 예상 요금

tts_quote

Read-only

합성·정규화 예상 요금과 최대 예약금을 조회합니다. 실제 정산액은 완료된 작업의 billing을 확인하세요. [무료]

Input Schema

TableJSON Schema

Name	Required	Description
`pace`	No	말 속도 배율 0.5~2.0. 1이 기본
`text`	No	합성 본문
`tone`	No	용도·톤. 생략 시 기본
`pitch`	No	음높이 -12~12 반음. 0이 기본
`style`	No	자유 서술 낭독 스타일
`accent`	No	억양. 생략 시 표준어
`engine`	No	기본 gemini
`emotion`	No	감정 표현. 생략 시 기본
`speakers`	No	화자 이름 → {voice_id, style, emotion, tone, accent, pace, pitch, volume_gain_db}
`voice_id`	No	목소리 ID. 생략 시 엔진 기본 목소리
`utterances`	No	발화 목록
`multi_speaker`	No	멀티화자. Gemini는 화자 2명까지 한 호출, ChatGPT는 발화별 목소리 대화
`normalize_text`	No	기본 true
`volume_gain_db`	No	음량 보정 -12~12 dB. 0이 기본

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 5, 2026

addedInput schema / properties / style

Added value: +{
+  "description": "자유 서술 낭독 스타일",
+  "maxLength": 1000,
+  "type": "string"
+}

changedInput schema / properties / voice_id / description

Previous value: -"목소리 ID"New value: +"목소리 ID. 생략 시 엔진 기본 목소리"

removedInput schema / required
```
Removed value: -[
-  "voice_id"
-]
```

Changed11 schema fields changedOct 5, 2026

addedInput schema / properties / accent

Added value: +{
+  "description": "억양. 생략 시 표준어",
+  "enum": [
+    "standard",
+    "seoul",
+    "gyeongsang",
+    "jeolla",
+    "chungcheong"
+  ],
+  "type": "string"
+}

addedInput schema / properties / emotion

Added value: +{
+  "description": "감정 표현. 생략 시 기본",
+  "enum": [
+    "neutral",
+    "calm",
+    "cheerful",
+    "excited",
+    "sad",
+    "serious",
+    "friendly",
+    "empathetic",
+    "confident",
+    "gentle",
+    "whisper",
+    "narration"
+  ],
+  "type": "string"
+}

changedInput schema / properties / engine / description

Previous value: -"기본 apick"New value: +"기본 gemini"

changedInput schema / properties / engine / enum

Previous value: -[
-  "apick",
-  "gemini"
-]New value: +[
+  "gemini",
+  "openai"
+]

removedInput schema / properties / fallback_policy

Removed value: -{
-  "description": "전환 정책",
-  "enum": [
-    "never",
-    "queue_full",
-    "busy"
-  ],
-  "type": "string"
-}

addedInput schema / properties / multi_speaker

Added value: +{
+  "description": "멀티화자. Gemini는 화자 2명까지 한 호출, ChatGPT는 발화별 목소리 대화",
+  "type": "boolean"
+}

addedInput schema / properties / pace

Added value: +{
+  "description": "말 속도 배율 0.5~2.0. 1이 기본",
+  "type": "number"
+}

addedInput schema / properties / pitch

Added value: +{
+  "description": "음높이 -12~12 반음. 0이 기본",
+  "type": "number"
+}

addedInput schema / properties / speakers

Added value: +{
+  "additionalProperties": {},
+  "description": "화자 이름 → {voice_id, style, emotion, tone, accent, pace, pitch, volume_gain_db}",
+  "propertyNames": {
+    "type": "string"
+  },
+  "type": "object"
+}

addedInput schema / properties / tone

Added value: +{
+  "description": "용도·톤. 생략 시 기본",
+  "enum": [
+    "narration",
+    "news",
+    "audiobook",
+    "documentary",
+    "ad",
+    "conversation",
+    "announcement",
+    "tutorial",
+    "storytelling"
+  ],
+  "type": "string"
+}

addedInput schema / properties / volume_gain_db

Added value: +{
+  "description": "음량 보정 -12~12 dB. 0이 기본",
+  "type": "number"
+}

AddedOct 4, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds real behavioral context: the result is an estimate plus a maximum reservation deposit, actual charges differ and must be read from completed-job billing, and the call is free ([무료]). These are meaningful traits not present in the annotations.

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?

Three short sentences with zero filler; the purpose is front-loaded, followed by the estimate-vs-actual caveat and the free-cost marker. Every sentence earns its place.

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 read-only pricing tool with no output schema and fully documented parameters, the description covers purpose, cost model, and the estimate/settlement distinction. The only gap is that it does not say the quote is computed from the same synthesis payload used by the create tools, which matters given the nested speakers/utterances inputs.

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% with 14 well-documented parameters, so the schema carries parameter semantics and the baseline is 3. The description adds nothing about which parameters drive the quote (text length, engine, speakers), but is not expected to given full schema coverage.

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?

States a specific verb and resource: query the estimated cost of synthesis/normalization plus the maximum reservation deposit. It also distinguishes itself from the actual-billing path by telling the agent that real settlement is found in completed jobs' billing. It does not name the sibling tool that provides billing, so it stops short of a 5.

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?

Usage is implied rather than stated: the tool is for getting a cost estimate, and the alternative (completed-job billing) is mentioned for actual amounts. It never says explicitly to call this before tts_jobs_create or how it relates to tts_options, leaving the when-to-use to inference.

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

All APICK 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.

TTS 예상 요금

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources