Skip to main content
Glama
Sign In

Claix

by dev.claix
OverviewDiscussionsAdmin

PDF to Markdown

claix.markdown.pdf
Read-onlyIdempotent

Convert PDF to Markdown (POST /api/pdf-markdown). No schema_id. Optional save=true inserts into the connected DB using Markdown rules and may return row_id; omit/false returns markdown only.

Input Schema

NameRequiredDescriptionDefault
saveNoWhen true, insert into the connected DB using Markdown rules and may return row_id. Omit or false: return markdown only.
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.
file_pathNoURL HTTPS pública del archivo a procesar. Ejemplo: https://cdn.example.com/factura.pdf. No uses rutas locales del PC del usuario.
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

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

B3.3/5.0
Behavior1/5

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

The description says save=true 'inserts into the connected DB', a write operation, while annotations declare readOnlyHint=true. This directly contradicts the structured safety metadata instead of reconciling it.

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?

Compact and front-loaded: conversion purpose first, then the key save flag and DB behavior. The 'No schema_id' note is a useful fragment rather than wasted prose.

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?

With a full input schema and an output schema, the description need not explain parameters or return values, and it does cover the optional save/row_id outcome. However, it fails to reconcile that write behavior with the readOnly annotation, leaving a potentially misleading context for the agent.

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 all five parameters are already documented in the input schema. The description repeats the save behavior but adds no parameter meaning beyond what the schema provides.

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?

States a specific verb and resource: 'Convert PDF to Markdown'. The name, title, and endpoint make it distinguishable from sibling extraction and other markdown conversion tools without needing to open 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?

Clarifies the save=true vs omit/false behavior and notes 'No schema_id', which gives some usage context. It does not compare against alternatives like extract.pdf or agent.pdf, so the agent receives no explicit when-to-use routing guidance.

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