Skip to main content
Glama
wenlan-app

Wenlan

Official
by wenlan-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Rust
Local

distill

DestructiveIdempotent

Synthesize new memories into Wenlan wiki pages; rebuild a single page, entity, or space, and optionally override user edits.

Instructions

Trigger Wenlan's distillation pass. With no target, runs a full pass that clusters new memories into pages and refreshes the wiki view. With a target, scopes the pass: a page id (page_* or concept_*) re-distills that single page, an entity name scopes clustering to that entity, a space value (e.g. work, personal) scopes to that space. With force=true on a page target, clears the user-edited guard and can replace the page prose during rebuild. Rebuild may send page and source material to the daemon's configured external LLM provider. Use when the user explicitly asks to synthesize, distill, or rebuild a page. With a model source chosen the daemon also distills in the background, so don't trigger redundantly; without one, nothing distills in the background.

Input Schema

NameRequiredDescriptionDefault
forceNoWhen true, clears the user_edited flag on the target page before recompile. Use for /distill rebuild <page> to explicitly wipe user prose and regenerate from sources. Only valid when target is a single page id; the daemon ignores it otherwise. Requires daemon LLM.
targetNoOptional target scope. Accepts a page id (`page_*` or `concept_*`) to re-distill that single page, an entity name (e.g. `Wenlan`, `Alice`) to scope clustering to that entity, or a space value (e.g. `work`, `personal`) to scope to that space. Omit for a full pass over any clusters with new sources. The daemon resolves the string and falls back with a hint payload if nothing matches.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.19.3

TDQS

A4.6/5.0
Behavior5/5

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

The description goes beyond the annotations by explaining that force=true clears the user-edited guard and can replace page prose, and that rebuild may send page and source material to an external LLM provider. These are important side effects that complement the destructiveHint and openWorldHint annotations rather than contradicting them.

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 then organizes target behavior, force semantics, external LLM implications, and usage guidance. It is somewhat dense and repeats a few schema points, but the structure is clear and every section is useful.

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

Completeness5/5

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

For a complex, side-effecting operation with no output schema, the description covers invocation modes, force implications, external LLM exposure, background behavior, and when to call it. Nothing essential for selecting or invoking the tool correctly is missing.

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?

The schema already documents both parameters at 100% coverage, so the baseline is 3. The description reinforces the target scopes and force behavior, but much of that information is already present in the schema 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?

The description names a specific action, 'Trigger Wenlan's distillation pass,' and clearly distinguishes the no-target full pass from targeted re-distillation. It specifies the accepted target forms (page id, entity name, space), making the tool's scope and resource precise.

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

Usage Guidelines5/5

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

It explicitly says to use the tool when the user asks to synthesize, distill, or rebuild a page, and it warns against redundant triggering when the daemon already distills in the background. This gives both the triggering condition and the condition under which not to call it.

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