Skip to main content
Glama

kurdish-tts-stt

by com.kurdishtts
OverviewDiscussionsAdmin

Start live Kurdish transcription session (listening, not speaking)

start_streaming_transcription
Destructive

Open a live speech-to-text session for LISTENING — a microphone or audio stream you transcribe in real time. This does NOT make anything speak; to speak Kurdish use synthesize_speech, or POST https://www.kurdishtts.com/api/tts-stream for progressive audio. WARNING: calling this immediately consumes one streaming session from your STT plan quota — only call it when you are ready to connect. Returns a websocket_url: open it, stream PCM16 mono 16kHz audio chunks, send {"type": "finalize"} to flush and {"type": "done"} to close. Session duration is limited by plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dialectYesDialect that will be spoken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • 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"
-}
    • changedInput schema / required
      Previous value: -[
-  "dialect",
-  "context"
-]New value: +[
+  "dialect"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations mark this non-idempotent and destructive, and the description adds real behavioral detail beyond them: it consumes a streaming session from the plan quota immediately, returns a websocket_url, requires PCM16 mono 16kHz chunks, and defines the finalize/done control messages plus a plan-limited session duration. That is substantial disclosure for a mutation-style 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-loads the LISTENING scope, then the exclusion, then the quota warning, then the protocol. Dense but every clause carries operational information; the only mild cost is the density of the websocket protocol detail in a single paragraph.

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?

No output schema exists, yet the description explains the return value (websocket_url) and exactly how to consume it, including audio format and close semantics. An agent has everything needed to call and drive the session correctly.

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% with a single enum dialect parameter fully documented in the schema, so the baseline is 3. The description adds nothing about the dialect parameter (e.g., which dialects the STT model supports), so it neither compensates nor detracts.

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+resource (open a live speech-to-text session) and immediately scopes it as LISTENING only, explicitly naming the contrasting sibling synthesize_speech for the speaking direction. An agent can distinguish it from synthesize_speech and transcribe_audio from the first sentence alone.

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?

Explicit when-to-use (only when ready to connect), when-not (does not make anything speak), and the alternative route for the opposite capability (synthesize_speech or the tts-stream endpoint). The quota warning gives a concrete precondition for calling.

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 toolsInspect
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