Skip to main content
Glama

kb_ingest_dir

Batch ingest markdown files from a directory into the knowledge base, with control over file patterns, recursion, and chunking strategies.

Instructions

Batch ingest directory of markdown files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dir_pathYesDirectory to scan
patternNoFile pattern (e.g., *.md)*.md
strategyNochunked
recursiveNoScan subdirectories
exclude_patternsNoPatterns to exclude
authorNoWho is ingesting (optional, defaults to None)
source_typeNoSource type for attribution (defaults to 'system' since ingestion is automated)system
confirm_productionNoRequired (true) to ingest more than 100 files when LORE_ENV=production. Guards against accidental bulk writes; not required for smaller ingests or non-prod.
Behavior1/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Batch ingest' without revealing destructive potential, authentication requirements, rate limits, or what happens to existing data. This is insufficient for a tool with 8 parameters and no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (5 words) and front-loaded, but it lacks structure and additional context. While concise, it is under-specified for a tool with multiple parameters and siblings.

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?

Given the tool's complexity (8 parameters, no output schema, no annotations), the description is incomplete. It does not explain key parameters like 'strategy' or the production guard, nor does it describe the return value or batch behavior.

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 88%, with all parameters having descriptions. The tool's description adds no additional meaning beyond what the schema provides, meeting the baseline of 3.

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 'Batch ingest directory of markdown files' clearly specifies the verb ('ingest') and resource ('directory of markdown files'), distinguishing it from the sibling tool 'kb_ingest_doc' which likely handles single documents.

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 no guidance on when to use this tool versus alternatives like 'kb_ingest_doc' or 'kb_add'. The schema includes a 'confirm_production' parameter hinting at production safeguards, but the description does not mention usage context or preconditions.

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/davidgut1982/lore-mcp'

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