Skip to main content
Glama

ai_tools_transcribe

[$x402 pago por llamada] Transcribe audio con Whisper (Workers AI). Acepta multipart con campo file.

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": {
      "file_base64": "<file_base64>"
    },
    "name": "ai_tools_transcribe"
  }
}

Input Schema

NameRequiredDescriptionDefault
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.
file_base64YesContenido del archivo codificado en base64 (o data URL). Se convierte a multipart/form-data internamente.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With zero annotations, the description carries the full burden, and it does disclose two behavioral facts an agent cannot get elsewhere: the call is metered under x402 and the backend is Whisper on Workers AI. It omits what most matters behaviorally — supported audio encodings, duration/size caps, rate limits, and whether a failed payment attempt consumes quota. It also says the tool 'Acepta multipart con campo `file`', which does not match the actual `file_base64` parameter (the schema notes internal conversion), a mild but real source of confusion rather than a direct annotation contradiction.

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?

Two short sentences with no filler, and the cost signal is front-loaded before the operation description. Minor deduction because the payment tag is bracketed boilerplate and the second sentence's multipart claim is misleading relative to the schema.

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

Completeness3/5

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

For a two-parameter tool with complete schema coverage and no output schema, the description covers the essentials: what it does, which engine, and that it is paid per call. It is incomplete on the things an agent would still need — the return shape (plain text vs. JSON/timestamps) and any input constraints — leaving the caller to discover them by trial.

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 description coverage is 100%, so both `x_payment` and `file_base64` (including the base64/data-URL detail and the 402 fallback) are already fully documented in structured data; baseline 3 applies. The description adds nothing about parameter semantics and in fact refers to a field named `file`, which does not correspond to any parameter, so it does not compensate for what the schema already handles well.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource: 'Transcribe audio con Whisper (Workers AI)', which is unambiguous and clearly distinct from every sibling (no other transcription tool exists in the list). The only noise is the bracketed payment tag, which is pricing metadata rather than purpose. It falls short of 5 only because it does not name a sibling/alternative it must not be confused with.

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?

'[$x402 pago por llamada]' signals that each call is billable, which is a useful invocation precondition, and the input schema independently explains the 402 fallback when x_payment is omitted. However, the description gives no explicit when-to-use guidance, no note about audio formats or size limits, and no indication of when an agent should prefer another tool. Usage is merely implied by the tool's name and the schema.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources