Skip to main content
Glama
u9401066

asset-aware-mcp

by u9401066

ingest_documents

Process PDF files to extract text and images, generate structured Document Manifests, and optionally index into a knowledge graph for precise asset retrieval.

Instructions

Process PDF files and create Document Manifests.

ETL Pipeline:

  1. Extract text (to markdown) and images

  2. Generate structured Document Manifest

  3. Index in LightRAG (if enabled)

Args: file_paths: List of absolute paths to PDF files async_mode: Kept for backwards compatibility. PDF ingestion is routed to a background job from the MCP tool layer to keep stdio clients responsive. use_marker: If True, use Marker for structured parsing (slower but more accurate). Produces blocks.json with bbox/coordinates for precise source tracking. Default False uses PyMuPDF (faster but less structured). marker_max_pages_per_chunk: When using Marker, split PDFs into fixed-size page chunks. Set 0 to use the safe automatic strategy. extract_figures: When using Marker, control whether image crops are extracted and saved. Disable this first for image-heavy textbooks to reduce memory pressure. page_ranges: 1-indexed inclusive page ranges applied to every input file, e.g. ["1-50", "120-160"].

Returns: Job ID for tracking progress with get_job_status.

Example: # Async (recommended for large files): ingest_documents(["/papers/study1.pdf"]) # Then check status: get_job_status("job_xxx")

# With Marker for precise source tracking:
ingest_documents(["/papers/textbook.pdf"], use_marker=True)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathsYes
async_modeNo
use_markerNo
ocr_enabledNo
ocr_languageNoeng
rotate_pagesNo
deskewNo
marker_max_pages_per_chunkNo
extract_figuresNo
index_knowledge_graphNo
page_rangesNo
ctxNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Without annotations, the description carries the full burden. It discloses async routing, differences between Marker and PyMuPDF, and memory considerations for extract_figures. However, it omits details like file modification safety, authentication needs, and error handling, leaving gaps.

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 well-structured with sections for ETL pipeline, Args, Returns, and Example. It is front-loaded with purpose. However, a few sentences are slightly redundant (e.g., 'Process PDF files' appears twice). Overall efficient.

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?

Given the complexity (12 parameters, no annotations, output schema exists), the description covers the main workflow and key parameters, but misses several optional parameters and does not address error scenarios, concurrency, or rate limits, making it moderately complete.

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?

Only 6 of 12 parameters are described in the description, while schema coverage is 0%. The described parameters have useful context (e.g., page_ranges format, use_marker trade-offs), but missing parameters like ocr_enabled, rotate_pages, and deskew leave the agent uninformed about significant options.

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 clearly states it processes PDF files and creates Document Manifests, with a specific verb and resource. However, it does not explicitly differentiate from sibling tools like 'ingest_docx' or 'convert_document', missing an opportunity to clarify scope.

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?

The description provides examples and notes async mode for large files, but does not explain when to use this tool versus alternatives. No comparison with sibling tools like 'ingest_docx' or 'parse_pdf_structure' is given, leaving the agent without decision guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/u9401066/asset-aware-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server