Alcoven

List documents

list

Read-only

Lists what is in a folder or in the whole project, newest change first, with who changed each and whether it changed since this person last opened it; files with their type and size. With a document's address, it lists the document's sections; with a file's, it says what the file is.

Input Schema

Name	Required	Description
`detail`	No	short, the default: one line for each item (its § address, title, who changed it and when, whether it changed since the person looked, and its first line), the newest 50 changes first, then how many more. full: each item with its first line on a line of its own, up to 200.
`folder`	No	A folder path like research or src/components, or a document's § address for its sections. Empty: everything.
`project`	No	The project's slug, from open_project, like acme. Not needed when a § address names the project, or when the person is on one project.

Output Schema

Name	Required	Description	Default
`more`	No
`items`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 26, 2026

addedInput schema / properties / detail

Added value: +{
+  "description": "short, the default: one line for each item (its § address, title, who changed it and when, whether it changed since the person looked, and its first line), the newest 50 changes first, then how many more. full: each item with its first line on a line of its own, up to 200.",
+  "enum": [
+    "short",
+    "full"
+  ],
+  "type": "string"
+}

First observedOct 22, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already establish that this is a safe read-only operation. The description adds useful behavior beyond that: newest-change-first ordering, who changed items, whether they changed since last viewed, and file type/size, but it does not mention limits or auth/rate-limit behavior.

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 around listing folder/project contents and uses only two sentences with no filler. The second sentence is dense and slightly run-on, but every clause carries functional meaning.

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

Completeness4/5

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

With rich annotations, a complete input schema, and an output schema, the description covers the main modes and return-relevant behavior adequately. It does not need to explain return formatting, but it also omits detail-mode limits and alternative-tool routing.

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?

Schema description coverage is 100%, so the schema already documents folder, project, and detail modes thoroughly. The description adds one nuance not in the schema: a file address makes it identify what the file is, but most parameter meaning is already supplied by the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear verb and resource: it lists folder/project contents, document sections, or file identity. It does not explicitly differentiate itself from siblings such as search, grep, read, or what_changed, so it falls short of a 5.

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

Usage Guidelines2/5

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

The description explains the listing modes but gives no explicit when-to-use guidance or alternatives. An agent is not told when to choose this over search, grep, read, or what_changed.

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

All Alcoven tools Inspect

Try in Browser

Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?