Skip to main content
Glama
enriquecatala

mcp-lightrag

ingest_batch

Recursively index files in a directory matching include patterns to batch ingest them into the LightRAG knowledge graph.

Instructions

Recursively index all files in a directory that match specific patterns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
directory_pathYesAbsolute path to the directory to scan
recursiveNoIf True, scans subdirectories recursively
max_depthNoMaximum depth for recursive scanning
include_patternsNoList of glob patterns for files to include (e.g. ['*.txt', '*.md'])
ignore_patternsNoList of glob patterns for files to exclude
Behavior2/5

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

No annotations provided, so description bears full burden. It lacks disclosure on side effects (e.g., overwriting, idempotency, indexing process, error behavior, or auth requirements).

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?

Single sentence, front-loaded with core action, no wasted words.

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?

Five parameters, no output schema or annotations, yet description omits return value, failure modes, and behavioral nuance for a batch operation.

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 covers all parameters with 100% description coverage; the minimal description adds no extra semantic value beyond summarizing the tool's purpose.

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?

Description clearly states the tool recursively indexes files matching patterns in a directory, which distinguishes it from single-file siblings like ingest_file and ingest_text.

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?

Implied usage for batch directory indexing but no explicit guidance on when to use this tool over alternatives or prerequisites.

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/enriquecatala/mcp-lightrag'

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