basic-memory

Find files

bm_find

Read-onlyIdempotent

Find notes recursively in a Basic Memory project by filename glob or frontmatter filters, restrict results to a folder, and return selected frontmatter fields to locate matching Markdown files.

Instructions

Find files in a Basic Memory project, recursively. With name, match file names against a glob ('meeting'). With filters, match notes by frontmatter, e.g. {"status": "active"} or {"priority": {"$in": ["high"]}}, and with fields return just those frontmatter values per note. path limits the search to a folder. For ranked text or meaning search, use bm_search.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "bm_find"
  }
}

Input Schema

Name	Required	Description	Default
`name`	No	File-name glob, e.g. '*.md'. Not with `filters`.
`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.	/
`depth`	No	Folder levels to search (1-10).
`fields`	No	Frontmatter fields to return per note (dot paths allowed), e.g. ["title", "priority"]. Needs `filters`.
`filters`	No	Frontmatter filters as {field: condition}. Nested fields use dot notation ("schema.confidence"). A condition is a value for equality ({"status": "draft"}), null for absent-or-null ({"owner": null}), a list for contains-all ({"tags": ["a", "b"]}), or an operator object with $gt, $gte, $lt, $lte, $in, $between, $contains or $exists, e.g. {"priority": {"$in": ["high"]}}. Several operators on one field AND together.
`project`	Yes	Required project name, 'workspace/project', or project external id. Discover projects with bm_project(command='list'). Paths are relative to this project; a qualified path must agree with it.
`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.

Changed7 schema fields changedOct 31, 2026

removedInput schema / properties / project / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / project / default
```
Removed value: -null
```

changedInput schema / properties / project / description

Previous value: -"Project name, 'workspace/project', or project external id. Omit to use the default project."New value: +"Required project name, 'workspace/project', or project external id. Discover projects with bm_project(command='list'). Paths are relative to this project; a qualified path must agree with it."

addedInput schema / properties / project / minLength
```
Added value: +1
```
addedInput schema / properties / project / type
```
Added value: +"string"
```
addedInput schema / required
```
Added value: +[
+  "project"
+]
```

changedOutput schema / properties / result / anyOf

Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]

Addedv0.24.1Oct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare this as read-only, idempotent, non-destructive, and not open-world. The description adds meaningful behavior beyond annotations: recursive traversal, frontmatter-based filtering, and projecting only requested frontmatter fields per note. It does not discuss permissions, but for a read-only search tool the added behavioral detail is solid.

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?

The description is four sentences, front-loaded with the core purpose, then organized by query mode, and ends with the key alternative. There is no filler and every sentence contributes to selecting or invoking the tool correctly.

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?

For a 9-parameter tool with a detailed schema, high schema coverage, annotations, and an output schema, the description covers the main behavior and the key alternative. Minor gaps around pagination, depth, and `output_format` are handled by the schema, so the definition is complete enough for correct selection and invocation.

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 89% and the schema itself contains detailed parameter documentation and examples. The description reinforces `name`, `filters`, `fields`, and `path` with examples, but adds little beyond the structured schema and does not explain pagination, depth, project resolution, or `output_format`.

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 states a specific verb and resource: 'Find files in a Basic Memory project, recursively.' It clearly enumerates the main query modes (`name`, `filters`, `fields`, `path`) and explicitly distinguishes this tool from `bm_search` for ranked text or meaning search.

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?

Useful usage context is given for `name`, `filters`, `fields`, and `path`, and the description explicitly routes ranked text/meaning search to `bm_search`. However, it does not mention that `name` cannot be combined with `filters` (that constraint is only in the schema) and does not distinguish usage from siblings such as `bm_list`.

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

Deploy Server