lilbee

Overview Schema Source Related Servers Discussions Admin

add

Index files, directories, or single URLs into lilbee's knowledge base and sync them. Use crawl for full sites; remote paths resolve on the lilbee host.

Instructions

Add files, directories, or URLs to the knowledge base, then sync. Paths are absolute and resolve on the machine running lilbee, not the caller's when the server is remote. URLs are fetched as single pages; use crawl for sites.

Input Schema

TableJSON Schema

Name	Required	Description
`ocr`	No	Which pages OCR reads.
`force`	No
`paths`	Yes
`ocr_timeout`	No
`render_mode`	No	How a crawl fetches pages. ``http`` uses no browser; ``browser`` runs Chromium with JS.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv1.0.16Oct 20, 2026

removedInput schema / $defs

Removed value: -{
-  "CrawlRenderMode": {
-    "description": "How a crawl fetches pages. ``http`` uses no browser; ``browser`` runs Chromium with JS.",
-    "enum": [
-      "http",
-      "browser"
-    ],
-    "title": "CrawlRenderMode",
-    "type": "string"
-  }
-}

removedInput schema / properties / enable_ocr
```
Removed value: -{
-  "type": "boolean"
-}
```

addedInput schema / properties / ocr

Added value: +{
+  "description": "Which pages OCR reads.",
+  "enum": [
+    "auto",
+    "all",
+    "off"
+  ],
+  "type": "string"
+}

removedInput schema / properties / render_mode / $ref
```
Removed value: -"#/$defs/CrawlRenderMode"
```

addedInput schema / properties / render_mode / description

Added value: +"How a crawl fetches pages. ``http`` uses no browser; ``browser`` runs Chromium with JS."

addedInput schema / properties / render_mode / enum
```
Added value: +[
+  "http",
+  "browser"
+]
```
addedInput schema / properties / render_mode / type
```
Added value: +"string"
```

Changed15 schema fields changedv1.0.2Jul 22, 2026
- removedInput schema / properties / enable_ocr / anyOf
```
Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / enable_ocr / default
```
Removed value: -null
```
- removedInput schema / properties / enable_ocr / title
```
Removed value: -"Enable Ocr"
```
- addedInput schema / properties / enable_ocr / type
```
Added value: +"boolean"
```
- removedInput schema / properties / force / default
```
Removed value: -false
```
- removedInput schema / properties / force / title
```
Removed value: -"Force"
```
- removedInput schema / properties / ocr_timeout / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / ocr_timeout / default
```
Removed value: -null
```
- removedInput schema / properties / ocr_timeout / title
```
Removed value: -"Ocr Timeout"
```
- addedInput schema / properties / ocr_timeout / type
```
Added value: +"number"
```
- removedInput schema / properties / paths / title
```
Removed value: -"Paths"
```
- addedInput schema / properties / render_mode / $ref
```
Added value: +"#/$defs/CrawlRenderMode"
```
- removedInput schema / properties / render_mode / anyOf
```
Removed value: -[
-  {
-    "$ref": "#/$defs/CrawlRenderMode"
-  },
-  {
-    "type": "null"
-  }
-]
```
- removedInput schema / properties / render_mode / default
```
Removed value: -null
```
- removedInput schema / title
```
Removed value: -"addArguments"
```

Changed2 schema fields changedv1.0.1Jun 17, 2026

addedInput schema / $defs

Added value: +{
+  "CrawlRenderMode": {
+    "description": "How a crawl fetches pages. ``http`` uses no browser; ``browser`` runs Chromium with JS.",
+    "enum": [
+      "http",
+      "browser"
+    ],
+    "title": "CrawlRenderMode",
+    "type": "string"
+  }
+}

addedInput schema / properties / render_mode

Added value: +{
+  "anyOf": [
+    {
+      "$ref": "#/$defs/CrawlRenderMode"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

First observedv1.0.0Jun 15, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose real behavior: the add is followed by a sync, paths are absolute and resolve on the lilbee host rather than the caller (critical for remote servers), and URLs are single-page fetches. It does not cover duplicate handling, idempotency, or what happens on partial failure, which matters for a mutating tool.

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?

Three tight sentences, front-loaded with the action, then the path-resolution caveat, then the sibling pointer. Every sentence earns its place and nothing is repeated from the schema.

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

Completeness3/5

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

An output schema exists, so return values need not be explained. For a mutation tool with five parameters and no annotations, however, the description leaves gaps around duplicate/overwrite behavior and two undocumented parameters, making it adequate but not fully self-sufficient.

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

Parameters2/5

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

Schema description coverage is only 40%, so the description must compensate, and it only explains `paths` (absolute, server-side resolution) plus URL behavior. `force` and `ocr_timeout` are undocumented in both places, and `ocr`/`render_mode` get no elaboration beyond their enum descriptions.

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?

States a specific verb and resource set (files, directories, URLs into the knowledge base) and pairs it with the implicit follow-up action (sync). It also explicitly distinguishes itself from the sibling `crawl`, so an agent can route between the two without inspecting either schema.

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?

Gives clear routing guidance: URLs are fetched as single pages, and `crawl` is named for whole sites. That covers the main ambiguity for this tool. It stops short of explicit exclusions against other ingestion siblings such as `import_dataset` or `init`, so it is clear context rather than complete when/when-not guidance.

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

add

Instructions

Input Schema

Output Schema

Schema Changelog

TDQS

Other Tools