Skip to main content
Glama

Claix

by dev.claix
OverviewDiscussionsAdmin

Agent mode audio to JSON

claix.agent.audio
Read-onlyIdempotent

Run audio extraction plus Agent mode reasoning. Requires is_agent_mode. Returns data[], agent_data, and log_id from spoken content. If source verification is enabled on the schema, fields are {value, source}. Formats: MP3, WAV, M4A, OGG. Max 12 MB / 10 minutes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
api_keyNoAPI key secreta de Claix. Ejemplo: claix_sk_abc123.... Opcional si la conexión MCP envía x-api-key en cabecera HTTP (recomendado en Smithery/Cursor).
filenameNoNombre original del archivo con extensión. Ejemplo: factura-2026-03.pdf. Ayuda a inferir el MIME cuando envías file_base64.
space_idNoOpcional. UUID del espacio de conocimiento donde agrupar el documento guardado. Ejemplo: 5b9e2c14-7d3a-4f8b-9e1c-6a0d4b8f2e7c. Debe pertenecer a la misma cuenta de la API key. Solo tiene efecto si el schema tiene la ventana de contexto activada, que es cuando el documento se guarda. Después puedes preguntar a todo el espacio con claix.space_context.ask.
file_pathNoURL HTTPS pública del archivo a procesar. Ejemplo: https://cdn.example.com/factura.pdf. No uses rutas locales del PC del usuario.
schema_idYesUUID del schema creado en el dashboard de Claix. Ejemplo: 550e8400-e29b-41d4-a716-446655440000. Llama a claix.schemas.list primero si no lo conoces.
file_base64NoArchivo codificado en Base64. Acepta data URLs (data:application/pdf;base64,...) o Base64 puro. Ejemplo de uso: adjunta el PDF/imagen del chat como Base64 antes de llamar a extract_*.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNoJSON payload from the Claix API (extracted records, schema list, or Excel export metadata).
errorNoHuman-readable error message when success is false.
successYesTrue when Claix returned a successful response. False when isError is set on the tool result.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly/openWorld/idempotent), the description discloses return shape (data[], agent_data, log_id), the conditional {value, source} structure when source verification is on, accepted formats, and hard limits (12 MB / 10 minutes). That is genuinely useful behavioral context, though it leaves the is_agent_mode requirement unresolved.

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?

The purpose is front-loaded in the first clause, and the following sentences each carry distinct, useful facts (returns, formats, limits). The 'Requires is_agent_mode' sentence is the one piece that does not clearly earn its place given no such parameter exists.

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?

An output schema exists, so the return-value explanation is safe to be brief, and the description covers formats, limits, and the source-verification variant. The main gap is the dangling is_agent_mode requirement and the absence of sibling routing guidance.

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 the six parameters are already documented and the baseline is 3. The description adds non-parameter constraints (formats, size/duration limits) but also references 'is_agent_mode', which is absent from the schema, creating ambiguity rather than added precision.

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?

The description uses a concrete verb+resource ("Run audio extraction plus Agent mode reasoning") and names the output, clearly distinguishing this from the plain extraction sibling. It does not, however, name claix.extract.audio explicitly, so the routing differentiator is implied by 'Agent mode reasoning' rather than stated.

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?

Usage is implied (audio input where agent-mode reasoning is wanted) but never stated as when-to-use vs. claix.extract.audio or the other claix.agent.* tools. The mention 'Requires is_agent_mode' hints at a precondition, but that parameter does not exist in the schema, which muddies rather than clarifies when the tool applies.

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

All Claix 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