kurdish-tts-stt

Kurdish text to speech

synthesize_speech

Convert Kurdish text (Sorani or Kurmanji) to speech audio. Requires a TTS API key; characters are billed against your plan. Max 600 characters per call over MCP — for longer texts call POST https://www.kurdishtts.com/api/tts-proxy directly (binary WAV, higher plan limits). Note: speed is caller-facing (higher = faster).

Input Schema

TableJSON Schema

Name	Required	Description
`text`	Yes	Kurdish text to synthesize.
`speed`	No	Playback speed, higher = faster. Default 1.
`context`	Yes	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."
`speaker_id`	Yes	Voice id from list_voices, e.g. sorani_1 or kurmanji_236. Dialect is derived from the prefix.
`model_version`	No	TTS model. Default v3; v4 requires a plan with v4 access.
`include_timestamps`	No	Return JSON with word-level timestamps and base64 audio instead of audio content.

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description takes on the burden and discloses the API key requirement, billing implications, character limits, and speed semantics ('speed is caller-facing (higher = faster)'). However, it does not describe the default response format (e.g., WAV or base64) or potential error behavior, which would add further transparency.

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 sentences, each earning its place: purpose, requirements/limitations, and speed note. It is front-loaded with the core action and contains no filler.

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?

The description covers purpose, authentication, billing, character limits, and an alternative for longer texts. Since there is no output schema, a brief note on the default response format (e.g., 'returns WAV audio' or 'returns base64 audio') would make it fully complete.

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 coverage is 100%, so the baseline is 3. The description mentions the 600-character limit and speed direction, but these are already present in the schema (maxLength=600, speed description). It adds minimal nuance beyond the structured fields.

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 'Convert Kurdish text (Sorani or Kurmanji) to speech audio,' which clearly identifies the operation and resource. This distinguishes it from sibling tools like transcribe_audio and start_streaming_transcription.

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 provides usage boundaries: 'Max 600 characters per call over MCP — for longer texts call POST ... directly.' It also clarifies the requirement for a TTS API key, making when-to-use vs. direct API clear.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation5/5

Each tool targets a distinct function: dialect discovery, voice listing, TTS synthesis, batch STT, and streaming STT. Even the two list_* tools have clearly differentiated outputs (language/script vs speaker IDs), leaving no ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun snake_case pattern: list_dialects, list_voices, start_streaming_transcription, synthesize_speech, transcribe_audio. No mixed conventions or irregular naming.

Tool Count5/5

Five tools is well-scoped for a TTS/STT service, covering metadata (dialects, voices) and core operations (synthesis, batch transcription, streaming transcription) without bloat or thinness.

Completeness5/5

The surface covers TTS (synthesize_speech), STT in both batch and streaming forms, and necessary metadata for dialect and voice selection. The redirect for large payloads to the direct API is a sensible design choice, not a gap.

Resources

Need Help?