Claix

Agent mode PDF to JSON

claix.agent.pdf

Read-onlyIdempotent

Run PDF extraction plus Agent mode reasoning. Requires is_agent_mode. Returns structured data[] and agent_data for business rules, booleans, or summaries defined in the schema.

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

A4.1/5.0

Behavior4/5

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

Annotations already declare the tool as read-only and idempotent. The description adds meaningful behavioral context beyond annotations: it explains that extraction is coupled with agent reasoning and describes the nature of returned agent_data, which is not evident from annotations alone. No contradictions found.

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 description is compact (two sentences) and front-loaded with the core purpose. The second sentence adds prerequisite and output info without unnecessary fluff. Slight ambiguity around 'Requires is_agent_mode' (as it is not a schema parameter) prevents a perfect score.

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?

Given the presence of an output schema, the description appropriately focuses on purpose and behavior rather than return format. It explains the nature of agent_data and the prerequisite, which is sufficient for understanding the tool within its sibling group. Could be more complete by explicitly stating file input methods, but these are already in the schema.

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 already provides 100% parameter descriptions, so baseline is 3. The description mentions 'Requires is_agent_mode' and references schema-defined rules, but does not add syntax or formats beyond what the schema covers. It neither enhances nor complicates parameter understanding.

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 states a specific verb ('Run') and resource ('PDF extraction') plus a differentiating feature ('Agent mode reasoning'). It clearly distinguishes this from claix.extract.pdf by mentioning agent-based processing, and the mention of 'structured data[] and agent_data' clarifies the output scope.

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

Usage Guidelines4/5

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

The description provides a clear precondition ('Requires is_agent_mode') and outlines the type of output ('business rules, booleans, or summaries defined in the schema'), which implies use cases. It does not explicitly name alternatives like claix.extract.pdf for simpler extraction, but the context of sibling tools makes the intended usage reasonably clear.

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?