Liste les voix bambara disponibles pour la synthese vocale, avec leur identifiant, leur nom et leur genre. A appeler avant kooma_text_to_speech : les identifiants varient d'un compte a l'autre et ne doivent jamais etre codes en dur.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries the full burden. It adds a useful behavioral fact: voice identifiers vary from one account to another and should not be hard-coded. The verb 'Liste' implies a read-only operation, though it does not explicitly state side-effect-free behavior. Still, this is sufficient for a simple listing tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loads the purpose, and contains no redundant wording. Every sentence earns its place: one for what the tool returns, one for when and why to call it.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter listing tool with no output schema, this description is complete: it names the resource, the output fields, the relationship to the sibling TTS tool, and an important data instability caveat. An agent has everything needed to invoke it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters and the schema is an empty object with 100% coverage. There is nothing for the description to add about parameters, so the 0-parameter baseline of 4 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states a specific verb ('Liste') and resource ('voix bambara disponibles pour la synthese vocale'), and specifies the returned fields: identifiant, nom, and genre. It also explicitly ties the tool to kooma_text_to_speech, distinguishing it from the other siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit when-to-use guidance: 'A appeler avant kooma_text_to_speech'. It also explains why it must be called first—voice IDs vary per account and must never be hard-coded—which gives the agent a clear decision rule.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a clearly distinct operation: voice discovery, speech synthesis, transcription from a URL, and translation. The only related pair, kooma_list_voices and kooma_text_to_speech, is explicitly designed as a dependency rather than an overlap.
All tools share the consistent kooma_ prefix and snake_case convention, with most names using straightforward verbs. kooma_text_to_speech breaks the verb-led pattern slightly, but the overall naming scheme remains predictable and readable.
With four tools, the server is tightly scoped to its core Bambara language tasks: text-to-speech, transcription, and translation. Every tool serves a distinct function and none feels redundant or extraneous.
The set covers the essential operations for each advertised capability, including a voice-list helper before synthesis and transcription from public URLs. Minor gaps such as a language-list helper for translation or local-file transcription are workable but not critical.
