Skip to main content
Glama
Sign In
Djelia MCP Server

Djelia MCP Server

Official
by djelia-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

transcribe

Transcribe Bambara speech to text using Djelia V2. Provide audio in base64 format and receive the transcription.

Instructions

Transcribe Bambara speech to text using Djelia V2.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "audio_base64": "<audio_base64>"
    },
    "name": "transcribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
audio_base64YesAudio file bytes encoded as base64. Supported: common formats (mp3, wav, m4a, ...).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions the model name and task, without detailing output format, supported audio formats beyond what the schema implies, or any limitations. This is minimal behavioral context.

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 a single, concise sentence that front-loads the action and subject. It contains no filler, every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is expected to provide more context about return values, error conditions, or behavioral expectations. It offers none, leaving significant gaps for an agent trying to invoke the tool 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?

The input schema provides a complete description of the single parameter (audio_base64) with format details, achieving 100% schema coverage. The tool description adds no additional parameter-specific meaning, so the baseline score of 3 applies.

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 uses the specific verb 'transcribe' and clearly identifies the resource ('Bambara speech') and the model ('Djelia V2'), distinguishing it from sibling tools like translate and text_to_speech.

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?

The description implies the tool is for transcribing Bambara audio, giving clear context, but it does not explicitly state when to use it versus alternatives or mention any exclusions. Sibling tools are provided, but the description itself lacks direct guidance.

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

Deploy Server

Other Tools