Skip to main content
Glama
Sign In
basic-memory

basic-memory

by basicmachines-co
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Manual

bm_man
Read-onlyIdempotent

Read the Basic Memory manual and search its pages by keyword to locate tool and command reference entries. Query with page names or words to find relevant documentation.

Instructions

Read the Basic Memory manual. With no arguments, the index of every page. page reads one page: 'bm-search(3)' for an MCP tool, 'grep(1)' for a shell command; a tool name such as 'bm_search' works too. query lists the pages that mention every word given, like man -k.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bm_man"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoThe page to read, e.g. 'bm-search(3)', 'grep(1)' or 'bm_search'.
queryNoWords to find in the manual; lists the pages that mention them all.
output_formatNotext

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / result / anyOf
      Previous value: -[
-  {
-    "additionalProperties": true,
-    "type": "object"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "additionalProperties": true,
+    "type": "object"
+  }
+]
  2. Addedv0.24.1

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds useful behavioral detail beyond that: what the no-argument form returns, what `page` accepts, and that `query` lists pages mentioning every supplied word, much like `man -k`.

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 explains each mode in one sentence. There is no redundancy or filler.

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 read-only annotations and an output schema present, the description does not need to explain return values or safety. It covers the main calling modes well, though it could briefly mention `output_format` behavior to be fully complete for all three parameters.

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?

The description adds real meaning for `page` by giving accepted forms like 'bm-search(3)', 'grep(1)', and bare tool names, and for `query` by clarifying the all-words matching behavior. It does not describe `output_format`, and schema description coverage is 67%, but the main parameters are well explained.

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 opens with a specific verb and resource: 'Read the Basic Memory manual.' It then clearly distinguishes the three modes (index, page, query), so an agent can immediately tell what the tool does without opening the 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?

It explains how to use each mode: no arguments for the index, `page` for one page, and `query` for keyword listing. It does not explicitly compare this tool to sibling tools like bm_search or bm_find, but the manual-reading context is clear and there are no misleading exclusions.

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

Deploy Server

Other Tools