Skip to main content
Glama
Sign In
LoreDocs

LoreDocs

Official
by labyrinth-analytics
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Import Directory

vault_import_dir

Bulk import files from a directory into a vault, extracting text for search indexing. Supports recursive traversal and merges tags from markdown.

Instructions

Bulk import all supported files from a directory into a vault.

Imports text files, PDFs, Word docs, Excel files, PowerPoints, and more. Each file becomes a separate document with text extracted for search indexing. Files over 30MB are skipped. Hidden files (starting with .) are skipped.

Supports Obsidian vaults: subdirectories are traversed recursively by default (set recursive=False for single-level import). Markdown files with YAML frontmatter tags (tags: [a, b] or block-list style) have those tags merged into the document.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vault": "<vault>",
      "directory": "<directory>"
    },
    "name": "vault_import_dir"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNo
vaultYes
categoryNoimported
directoryYes
recursiveNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.19

TDQS

A4.2/5.0
Behavior4/5

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

Beyond the annotations (all false, no safety hints), the description adds valuable behavioral details: files over 30MB are skipped, hidden files are skipped, subdirectories are traversed recursively by default, and YAML frontmatter tags are merged into documents. This gives the agent a good sense of what will happen during import, though it doesn't clarify behavior for existing documents or partial failures.

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?

The description is concise and well-structured: a clear purpose statement followed by relevant bullet-like behavior details. Every sentence adds value, no fluff, and it's front-loaded with the primary action.

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

Completeness4/5

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

For a bulk import tool with 5 parameters and an output schema, the description covers key aspects: supported formats, size limits, hidden files, recursion, and frontmatter handling. It doesn't explain the 'category' parameter or what happens on naming conflicts, but these are minor gaps given the output schema exists and the description is otherwise informative.

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 coverage is 0%, so the description must explain parameters. It clarifies 'directory' (the source path) and 'recursive' (set recursive=False for single-level) and partially describes tag handling via frontmatter. However, 'vault' and 'category' are not explained, and the 'tags' parameter's meaning (likely tags applied to all imported docs) is ambiguous—it might be confused with frontmatter tags.

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 opens with 'Bulk import all supported files from a directory into a vault,' using a specific verb (import), resource (directory into vault), and scope (bulk). It also lists supported file types and clearly distinguishes itself from siblings like vault_add_doc (single file) or vault_import_notion (Notion-specific).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool: when you need to bulk import files from a directory into a vault. It mentions recursive traversal and the ability to set recursive=False for single-level imports. However, it doesn't explicitly mention alternatives or when not to use it (e.g., for single-file import), but the purpose is unambiguous enough.

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

Deploy Server

Other Tools