Claix

Agent mode image to JSON

claix.agent.image

Read-onlyIdempotent

Run image extraction plus Agent mode reasoning. Requires is_agent_mode. Returns data[] and agent_data from visible content.

Input Schema

TableJSON Schema

Name	Required	Description
`api_key`	No	API 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).
`filename`	No	Nombre original del archivo con extensión. Ejemplo: factura-2026-03.pdf. Ayuda a inferir el MIME cuando envías file_base64.
`file_path`	No	URL HTTPS pública del archivo a procesar. Ejemplo: https://cdn.example.com/factura.pdf. No uses rutas locales del PC del usuario.
`schema_id`	Yes	UUID 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_base64`	No	Archivo 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

Name	Required	Description
`data`	No	JSON payload from the Claix API (extracted records, schema list, or Excel export metadata).
`error`	No	Human-readable error message when success is false.
`success`	Yes	True when Claix returned a successful response. False when isError is set on the tool result.

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint:false, so the safety profile is covered. The description adds return shape (data[] and agent_data) and the 'visible content' scope, but the unexplained 'Requires is_agent_mode' creates ambiguity about preconditions.

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 two short sentences, front-loaded with the action and output, with no filler. It is concise and easy to scan.

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?

Despite having a rich schema and output schema, the description leaves 'Agent mode' undefined and the is_agent_mode requirement unaddressable. It also does not clarify how the image should be provided or when to use this vs. the extraction-only siblings. The tool has 5 parameters and multiple input methods, so more context is needed.

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

Parameters2/5

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

Schema description coverage is 100%, so a baseline of 3 is appropriate. However, the description introduces 'is_agent_mode' as a requirement even though no such parameter exists in the schema, actively confusing parameter handling. It adds no useful parameter-level meaning beyond the schema.

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 specific verb ('Run') and names the resource ('image extraction plus Agent mode reasoning'), and the title clarifies the JSON output. It differentiates from claix.extract.image by adding Agent-mode reasoning. However, 'Agent mode' is unexplained jargon, so it is not fully self-contained.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given about when to choose this over siblings like claix.extract.image or claix.agent.pdf. The 'Requires is_agent_mode' line states a requirement but provides no context, and no alternatives or exclusions are mentioned.

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

All Claix tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.9/5.0

Disambiguation5/5

Every tool has a clearly distinct role: extract.* produces raw structured JSON, agent.* adds agent-mode reasoning, schemas.* manages schemas, and window_context.* handles persisted documents. Even the parallel extract/agent pairs for each format are disambiguated by the agent/group prefix and explicit descriptions about is_agent_mode.

Naming Consistency4/5

All tools follow a claix.<group>.<target> convention with lowercase snake_case, which is predictable and readable. The main inconsistency is action placement: extract.doc is verb-first while schemas.create is object-first, and convert.json_to_excel uses a noun phrase instead of a verb.

Tool Count4/5

At 17 tools, the set is slightly above the ideal 3-15 range, but each tool maps to a distinct endpoint or format variant. The parallel extract and agent families are justified by different processing modes, though they do make the surface feel a bit heavier than necessary.

Completeness4/5

The set covers schema lifecycle (create, list, delete), extraction for five major formats, agent-mode variants, document deletion, and window-context query/retrieval. Minor gaps include no schema update endpoint and no generic document listing/retrieval outside window_context.

Resources

Need Help?