Ingest a markdown file into a knowledge base with automatic change detection. Supports chunked or full ingestion with customizable chunk size, tags, and author attribution.
Ingest single markdown file into KB with change detection
| Name | Required | Description | Default |
|---|---|---|---|
| doc_path | Yes | ||
| strategy | No | chunked | |
| chunk_size | No | ||
| tags | No | ||
| overwrite | No | ||
| author | No | ||
| source_type | No | system |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.9.0Input schema / properties / strategy / enumPrevious value: -[
- "full",
- "chunked",
- "summary"
-]New value: +[
+ "full",
+ "chunked"
+]v0.8.5Input schema / additionalPropertiesAdded value: +falseInput schema / properties / author / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / author / defaultAdded value: +nullInput schema / properties / author / descriptionRemoved value: -"Who is ingesting (optional, defaults to None)"Input schema / properties / author / typeRemoved value: -"string"Input schema / properties / chunk_size / descriptionRemoved value: -"Max tokens per chunk (chunked strategy only)"Input schema / properties / doc_path / descriptionRemoved value: -"Absolute path to markdown file"Input schema / properties / overwrite / descriptionRemoved value: -"Replace existing KB entries from this doc"Input schema / properties / source_type / descriptionRemoved value: -"Source type for attribution (defaults to 'system' since ingestion is automated)"Input schema / properties / strategy / descriptionRemoved value: -"Ingestion strategy: full (one entry) or chunked (by sections). 'summary' is not provided by Lore (LLM-free); generate summaries in the caller — see issue #19."Input schema / properties / tags / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / tags / defaultAdded value: +nullInput schema / properties / tags / descriptionRemoved value: -"Additional tags"Input schema / properties / tags / itemsRemoved value: -{
- "type": "string"
-}Input schema / properties / tags / typeRemoved value: -"array"Output schema / (root)Previous value: -nullNew value: +{
+ "properties": {
+ "result": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "result"
+ ],
+ "type": "object",
+ "x-fastmcp-wrap-result": true
+}v0.8.4Input schema / properties / strategy / descriptionPrevious value: -"Ingestion strategy: full (one entry), chunked (by sections), summary (GPT summary)"New value: +"Ingestion strategy: full (one entry) or chunked (by sections). 'summary' is not provided by Lore (LLM-free); generate summaries in the caller — see issue #19."v0.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must carry full burden. It mentions change detection but does not explain what that entails (e.g., whether it checks for changes, how conflicts are handled). No disclosure of permissions, rate limits, or side effects beyond ingestion.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is extremely concise (one sentence) and front-loads the primary action. However, it sacrifices necessary detail, making it borderline under-specified.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 7 parameters, no schema descriptions, no annotations, and an existing output schema, the description is severely lacking. It does not clarify return values, change detection mechanics, or parameter interactions, leaving the agent with insufficient context for reliable invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, yet the description provides no explanation for any of the seven parameters (e.g., strategy, chunk_size, tags, overwrite, author, source_type). The agent has no insight into parameter purpose or constraints.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool ingests a single markdown file into KB with change detection, distinguishing it from directory-level operations like kb_ingest_dir and other KB tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives like kb_ingest_dir or kb_update. The mention of 'change detection' is vague and not explained in context of use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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