kurdish-tts-stt

List Kurdish TTS voices

list_voices

Read-onlyIdempotent

List available Kurdish text-to-speech voices. Returns speaker ids to use with synthesize_speech. Free metadata call — no credits consumed, no API key needed. Defaults to model_version "v3", the SAME default synthesize_speech uses — pass the same model_version to both, because a speaker id from one catalog does not exist in another. Results are paginated; the response reports total_count and which ids a free plan may render.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum voices to return. Default 25.
`gender`	No	Filter by voice gender.
`offset`	No	Number of voices to skip, for paging. Default 0.
`dialect`	No	Filter by dialect.
`model_version`	No	Voice catalog. Default "v3", matching synthesize_speech. v3 is the compatibility catalog; v4 is the large catalog (hundreds of voices); v5 is the curated catalog plus Cast and Studio voices, and requires a paid API plan.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`limit`	Yes
`offset`	Yes
`has_more`	Yes
`speakers`	Yes
`your_plan`	Yes
`total_count`	Yes
`model_version`	Yes
`returned_count`	Yes
`unique_speaker_ids`	Yes
`model_version_source`	Yes
`free_plan_speaker_ids`	Yes
`your_allowed_model_versions`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 15, 2026

changedInput schema / properties / dialect / enum

Previous value: -[
-  "sorani",
-  "kurmanji"
-]New value: +[
+  "sorani",
+  "kurmanji",
+  "badini"
+]

Changed5 schema fields changedSep 13, 2026

addedOutput schema / properties / speakers / items / properties / dialect_note
```
Added value: +{
+  "type": "string"
+}
```
addedOutput schema / properties / speakers / items / properties / reads_either_dialect
```
Added value: +{
+  "type": "boolean"
+}
```

changedOutput schema / properties / speakers / items / required

Previous value: -[
-  "free_plan",
-  "usable_by_you",
-  "requires_developer_plan"
-]New value: +[
+  "free_plan",
+  "usable_by_you",
+  "requires_developer_plan",
+  "reads_either_dialect"
+]

addedOutput schema / properties / unique_speaker_ids
```
Added value: +{
+  "type": "number"
+}
```

changedOutput schema / required

Previous value: -[
-  "model_version",
-  "model_version_source",
-  "your_plan",
-  "your_allowed_model_versions",
-  "total_count",
-  "returned_count",
-  "offset",
-  "limit",
-  "has_more",
-  "free_plan_speaker_ids",
-  "note",
-  "speakers"
-]New value: +[
+  "model_version",
+  "model_version_source",
+  "your_plan",
+  "your_allowed_model_versions",
+  "total_count",
+  "unique_speaker_ids",
+  "returned_count",
+  "offset",
+  "limit",
+  "has_more",
+  "free_plan_speaker_ids",
+  "note",
+  "speakers"
+]

Changed8 schema fields changedSep 13, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

removedInput schema / properties / context

Removed value: -{
-  "description": "Explain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): \"Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization.\"",
-  "type": "string"
-}

addedInput schema / properties / gender

Added value: +{
+  "description": "Filter by voice gender.",
+  "enum": [
+    "male",
+    "female"
+  ],
+  "type": "string"
+}

addedInput schema / properties / limit

Added value: +{
+  "description": "Maximum voices to return. Default 25.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}

changedInput schema / properties / model_version / description

Previous value: -"Voice catalog. v3 is the compatibility default; v4 has up to 664 voices; v5 is the curated catalog: 20 voices, plus 13 Cast and Studio voices on plans bought for the API."New value: +"Voice catalog. Default \"v3\", matching synthesize_speech. v3 is the compatibility catalog; v4 is the large catalog (hundreds of voices); v5 is the curated catalog plus Cast and Studio voices, and requires a paid API plan."

addedInput schema / properties / offset

Added value: +{
+  "description": "Number of voices to skip, for paging. Default 0.",
+  "minimum": 0,
+  "type": "integer"
+}

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "free_plan_speaker_ids": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "has_more": {
+      "type": "boolean"
+    },
+    "limit": {
+      "type": "number"
+    },
+    "model_version": {
+      "type": "string"
+    },
+    "model_version_source": {
+      "type": "string"
+    },
+    "note": {
+      "type": "string"
+    },
+    "offset": {
+      "type": "number"
+    },
+    "returned_count": {
+      "type": "number"
+    },
+    "speakers": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "dialect": {
+            "type": "string"
+          },
+          "free_plan": {
+            "type": "boolean"
+          },
+          "gender": {
+            "type": "string"
+          },
+          "id": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "requires_developer_plan": {
+            "type": "boolean"
+          },
+          "speaker_id": {
+            "type": "string"
+          },
+          "usable_by_you": {
+            "type": [
+              "boolean",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "free_plan",
+          "usable_by_you",
+          "requires_developer_plan"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "total_count": {
+      "type": "number"
+    },
+    "your_allowed_model_versions": {
+      "anyOf": [
+        {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "your_plan": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "model_version",
+    "model_version_source",
+    "your_plan",
+    "your_allowed_model_versions",
+    "total_count",
+    "returned_count",
+    "offset",
+    "limit",
+    "has_more",
+    "free_plan_speaker_ids",
+    "note",
+    "speakers"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 10, 2026

changedInput schema / properties / model_version / description

Previous value: -"Voice catalog. v3 is the compatibility default; v4 has up to 664 voices; v5 is the 21-voice curated catalog."New value: +"Voice catalog. v3 is the compatibility default; v4 has up to 664 voices; v5 is the curated catalog: 20 voices, plus 13 Cast and Studio voices on plans bought for the API."

Changed2 schema fields changedSep 4, 2026

changedInput schema / properties / model_version / description

Previous value: -"Voice catalog version. v4 (default) has 664 voices."New value: +"Voice catalog. v3 is the compatibility default; v4 has up to 664 voices; v5 is the 21-voice curated catalog."

changedInput schema / properties / model_version / enum

Previous value: -[
-  "v3",
-  "v4"
-]New value: +[
+  "v3",
+  "v4",
+  "v5"
+]

First observedAug 10, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it explicitly states 'no credits consumed, no API key needed', which is a free-call guarantee not in the annotations. It also discloses pagination behavior and the model_version default matching synthesize_speech. This is meaningful added context, though it doesn't describe the exact response structure (but an output schema exists).

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?

The description is compact and front-loaded: the core purpose is in the first sentence, followed by the most important usage constraint (model_version matching), then pagination and free-plan notes. Every sentence earns its place, and the critical warning about speaker id catalogs is placed early. No fluff or redundancy.

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?

For a read-only metadata list tool with 100% schema coverage, an output schema, and annotations covering safety, the description is complete. It covers the key cross-tool dependency (model_version must match synthesize_speech), pagination behavior, free-plan rendering info, and the no-credits/no-key fact. An agent has everything needed to call this tool correctly and interpret its results.

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 the schema already documents all 5 parameters thoroughly, including enums and defaults. The description adds some cross-parameter context (model_version default matches synthesize_speech, and the v3/v4/v5 distinction is already in the schema). It doesn't add much beyond the schema, but the baseline of 3 is appropriate because the schema carries the heavy lifting.

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?

The description states a specific verb ('List'), a clear resource ('available Kurdish text-to-speech voices'), and explicitly distinguishes its output from a sibling ('Returns speaker ids to use with synthesize_speech'). It also clarifies it is a metadata call, which differentiates it from synthesis and transcription siblings. This is a clear, specific purpose statement.

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?

The description explicitly tells the agent when to use this tool: to get speaker ids for synthesize_speech. It also gives a critical usage rule: pass the same model_version to both list_voices and synthesize_speech because speaker ids are catalog-specific. It also notes that results are paginated and that the response reports which ids a free plan may render, giving the agent actionable context for using the tool correctly.

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

All kurdish-tts-stt 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.

Resources

Need Help?