basic-memory

List folder

bm_list

Read-onlyIdempotent

List a Basic Memory project folder’s subfolders and files with titles, dates, and IDs; filter by glob, sort results, or list available projects from the root.

Instructions

List one folder of a Basic Memory project: its subfolders, then its files with title, date and id. bm_list('/') with no project lists the projects you can address; '/path' lists inside another project. Filter files with glob and order them with sort. For a recursive search by name or frontmatter, use bm_find.

Input Schema

Name	Required	Description	Default
`glob`	No	File-name glob, e.g. '.md' or 'meeting*'.
`page`	No	Page number.
`path`	No	A directory in the project, e.g. 'specs' or 'specs/active'. '/' is the project root; '<project>/path' addresses another project.	/
`sort`	No	File order. Folders always come first.
`project`	No	Project name, 'workspace/project', or project external id. Omit to use the default project.
`page_size`	No	Results per page (1-100).
`output_format`	No		text

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.24.1Oct 23, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral detail beyond that: ordering guarantees ('subfolders, then its files'), the fields returned per file, and cross-project addressing. It does not mention pagination behavior, which is the one notable gap.

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 core behavior, then addressing rules, then the sibling redirect. No filler and no repetition of schema text.

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 7 optional parameters, rich annotations and an output schema, the description covers the essentials an agent needs to pick and call this tool. The only missing piece is that results are paginated (page/page_size defaults), which an agent could otherwise miss.

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

Parameters4/5

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

Schema coverage is high at 86%, so the baseline is 3. The description still adds real meaning: it clarifies the special '/' form and the '<project>/path' cross-project addressing convention, and explains that glob and sort apply to files (not folders).

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 ('List one folder of a Basic Memory project') and immediately specifies the return shape: subfolders first, then files with title, date and id. It also explicitly distinguishes itself from the sibling bm_find, which does recursive name/frontmatter search.

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?

Gives concrete usage context: `bm_list('/')` with no project lists addressable projects, '<project>/path' lists inside another project. It names the alternative (bm_find) and the condition that selects it, plus notes where filtering (glob) and ordering (sort) belong.

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