List documents stored in AnythingLLM's local file tree to inspect available vector files before querying or embedding content.
List documents known to the AnythingLLM system (the document/vector file tree under localFiles).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. It usefully scopes the result to the localFiles document/vector tree, which clarifies what is enumerated, but says nothing about ordering, pagination, size limits, or permissions.
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?
A single front-loaded sentence with no filler, appropriately sized for a no-argument list tool, though it is content-light enough that one clause about the returned structure could have been added without bloat.
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?
With no annotations and no output schema, the description must stand in for return-value behavior. It identifies the scope of the listing but does not describe the shape of returned entries or whether workspace/embedding metadata is included, leaving a modest gap for a zero-param tool.
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?
The tool takes zero parameters, so there is no per-parameter semantics to explain; the baseline for a no-arg schema is 4.
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?
States a specific verb (List) and resource (documents) plus the scope (AnythingLLM's localFiles document/vector tree). An agent can distinguish it from workspace-management siblings like list_workspaces, though it doesn't explicitly name a contrast tool.
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?
Usage is implied by the simple listing semantics and the absence of any competing document-list sibling, but the description gives no explicit when-to-use guidance or relationship to tools like get_answer or update_embeddings that also touch documents.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.