Skip to main content
Glama

nest_scan

Scan a folder to extract and classify files into a SQLite Nest DB. Use dry-run to preview counts before writing, with local-only inference by default.

Instructions

Walk a drop folder, extract + classify its files, and write a canonical SQLite Nest DB. Returns structure only (counts by source status and fragment type) — never file content.

dry_run=True (default): classify and report counts WITHOUT writing the DB — inspect what a dump would become before committing it. dry_run=False writes. use_embed uses an Ollama embedding model when present (falls back to regex offline); use_llm escalates the uncertain tail to a text/vision model.

Inference stays on this machine by default. It is NOT unconditional: the seams post to $OLLAMA_HOST, and if that points off-box this tool requires the operator's standing consent.cloud_llm and denies without it. Classification sends document bodies, so where that host points is a privacy decision, not a performance one. (This docstring used to promise "nothing leaves the machine" flatly, which was true of the default and false of the variable.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ownerNo
app_idYes
folderYes
db_pathNo
dry_runNo
use_llmNo
use_embedNo
Behavior5/5

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

The description discloses side effects beyond the annotations: dry_run controls DB writes, return values exclude file content, inference is local by default but can leave the machine depending on OLLAMA_HOST, and document bodies are sent when off-box. It even corrects a previously overbroad privacy promise, which is unusually transparent.

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

Conciseness4/5

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

The description is front-loaded with the core action and output contract, then parameter behavior, then privacy edge cases. The final self-referential docstring correction is slightly meta but prevents reliance on an outdated promise. No filler sentences.

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?

It covers output shape, dry-run safety, model fallbacks, and privacy conditions thoroughly, which is essential since there is no output schema. However, required data parameters are undefined, and optional db_path/owner semantics are absent, leaving enough ambiguity to prevent confident invocation.

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 0%, so the description must explain parameters. It clarifies dry_run, use_embed, and use_llm well, but not the required app_id and folder, nor db_path and owner. The agent is left to guess the meaning of required parameters, which is a serious gap for a 7-parameter tool.

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 names a specific action set — walk a drop folder, extract/classify files, and write a SQLite Nest DB — and immediately clarifies the return contract: structure-only counts, never file content. This clearly distinguishes it from generic storage, search, or messaging siblings.

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?

Provides strong operational guidance: dry_run=True previews without writing, dry_run=False commits; use_embed/use_llm are explained by availability and fallback; and the off-box OLLAMA_HOST case is gated on consent.cloud_llm. It lacks an explicit 'use X instead' sibling route, so it stops short of 5.

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/willow-memory/willow-mcp'

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