Skip to main content
Glama
Sign In

Arabic Pipeline API

by io.github.skypantherr
OverviewDiscussionsAdmin

Transcribe audio

audio_transcribe
Read-onlyIdempotent

Transcribe Arabic or English speech to plain text. Send the audio as base64 (webm, mp3, wav or mp4); the payload limit is 12 MB of base64. Returns the transcript plus the model that produced it.

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": "audio_transcribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
mime_typeNoAudio MIME type, e.g. audio/webm.
audio_base64YesBase64-encoded audio file.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world; the description adds concrete operational context the annotations cannot: the 12 MB base64 payload ceiling, the accepted container formats (webm, mp3, wav, mp4), and the shape of the return (transcript plus model name). Synchronous-vs-async behavior and error modes for unsupported languages are still undisclosed.

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, zero waste, and the most actionable detail (input encoding) is placed immediately after the purpose. No repetition of the title or annotations.

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?

With no output schema the description carries the burden of the return value, which it does (transcript plus model). Enough to call it correctly; only latency/async behavior and handling of unsupported audio are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond the schema: it enumerates the accepted formats (the schema only gives 'audio/webm' as an example) and states the 12 MB size constraint. It doesn't clarify whether mime_type is required in practice or how it is inferred.

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 first sentence gives a specific verb (transcribe) and resource (Arabic or English speech to plain text), which no sibling tool (doc_extract, text_chunk, text_normalize) does. The agent can identify the tool's function without opening the schema.

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 language restriction (Arabic or English) implies when the tool applies, but there is no explicit statement of when to prefer an alternative, e.g., what to do with other languages or a text-input source. How to use is implied by the input-format instructions.

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

All Arabic Pipeline API 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