Skip to main content
Glama

Find files

bm_find
Read-onlyIdempotent

Find files recursively in a Basic Memory project by filename glob or frontmatter filters, and return selected fields. Limit searches to a folder or project.

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.

Input Schema

NameRequiredDescriptionDefault
nameNoFile-name glob, e.g. '*.md'. Not with `filters`.
pageNoPage number.
pathNoA directory in the project, e.g. 'specs' or 'specs/active'. '/' is the project root; '<project>/path' addresses another project./
depthNoFolder levels to search (1-10).
fieldsNoFrontmatter fields to return per note (dot paths allowed), e.g. ["title", "priority"]. Needs `filters`.
filtersNoFrontmatter 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.
projectNoProject name, 'workspace/project', or project external id. Omit to use the default project.
page_sizeNoResults per page (1-100).
output_formatNotext

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.24.1

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful operational context: recursive search, path scoping, frontmatter filtering, and projecting selected fields, though it does not restate pagination behavior or the `fields`-requires-`filters` constraint that appears in the schema.

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 front-loaded with the core purpose and then efficiently covers the main modes and the alternative tool. Every sentence earns its place, with no filler or repeated annotation metadata.

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 nine-parameter read-only search tool with a rich input schema, an output schema, and strong annotations, the description covers the essential selection and invocation context. It leaves pagination and some parameter interactions to the schema, which is acceptable given the 89% coverage but prevents a perfect score.

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%, so the schema already documents most parameters thoroughly, including the detailed `filters` operator grammar. The description reinforces `name`, `filters`, `fields`, and `path` with examples but does not add significant meaning beyond the schema, so the high-coverage baseline of 3 is appropriate.

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: find files in a Basic Memory project, recursively. It clearly distinguishes its modes (`name` glob, `filters` frontmatter matching, `fields` projection) and explicitly routes ranked text/meaning search to `bm_search`, so an agent can tell it apart from that sibling without opening either schema.

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?

Gives clear usage context for each major mode and names the alternative for ranked text or meaning search: use `bm_search`. It does not explicitly state the `name`/`filters` mutual exclusion in prose, although the schema does, so it falls short of fully explicit when-not guidance.

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