Skip to main content
Glama
davidgut1982

lore-mcp

by davidgut1982
OverviewSchemaRelated ServersScoreDiscussions
Python
Hybrid

kb_ingest_dir

Batch ingest markdown files from a directory into the knowledge base. Supports recursive scanning, chunked or full ingestion, and exclusion patterns.

Instructions

Batch ingest directory of markdown files

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dir_pathYes
patternNo*.md
strategyNochunked
recursiveNo
exclude_patternsNo
authorNo
source_typeNosystem
confirm_productionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changedv0.9.0
    • changedInput schema / properties / strategy / enum
      Previous value: -[
-  "full",
-  "chunked",
-  "summary"
-]New value: +[
+  "full",
+  "chunked"
+]
  2. Changed16 schema fields changedv0.8.5
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / author / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / author / default
      Added value: +null
    • removedInput schema / properties / author / description
      Removed value: -"Who is ingesting (optional, defaults to None)"
    • removedInput schema / properties / author / type
      Removed value: -"string"
    • removedInput schema / properties / confirm_production / description
      Removed value: -"Required (true) to ingest more than 100 files when LORE_ENV=production. Guards against accidental bulk writes; not required for smaller ingests or non-prod."
    • removedInput schema / properties / dir_path / description
      Removed value: -"Directory to scan"
    • addedInput schema / properties / exclude_patterns / anyOf
      Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "items": {
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / exclude_patterns / default
      Added value: +null
    • removedInput schema / properties / exclude_patterns / description
      Removed value: -"Patterns to exclude"
    • removedInput schema / properties / exclude_patterns / items
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / exclude_patterns / type
      Removed value: -"array"
    • removedInput schema / properties / pattern / description
      Removed value: -"File pattern (e.g., *.md)"
    • removedInput schema / properties / recursive / description
      Removed value: -"Scan subdirectories"
    • removedInput schema / properties / source_type / description
      Removed value: -"Source type for attribution (defaults to 'system' since ingestion is automated)"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "type": "object",
+  "x-fastmcp-wrap-result": true
+}
  3. First observedv0.7.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations exist, so description must cover behavior. It lacks details on atomicity, overwrite behavior, error handling, or required permissions.

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?

Single sentence is concise but overly terse; lacks front-loading of critical information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having an output schema and 8 parameters, the description explains nothing about return values, parameter effects, or prerequisites, making it very incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, and the description adds no meaning to any of the 8 parameters. It only repeats the basic 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?

Clearly states the tool ingests a directory of markdown files in batch. Among siblings, kb_ingest_doc handles single files, so this distinguishes as batch directory ingestion.

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?

Implies usage for directory ingestion but provides no explicit when-to-use or when-not-to-use guidance, nor comparisons to alternatives like kb_ingest_doc.

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