c2b
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| brain_searchC | Search ASM across vault pages, mapped code, and immediate shared-memory records. |
| brain_nodeB | Get full details of a brain node by id (e.g. 'vault:api-agent-allowlist', 'api:src/server/routes.py'). |
| brain_neighborsB | Neighbors of a node up to |
| brain_pathB | Shortest path between two brain nodes (BFS over all edge types). |
| brain_contextA | THE tool to call before touching a file: given an absolute or relative file path, returns what the brain knows — the matching node, its code neighbors, linked vault knowledge pages (gotchas/decisions about it), and recent cross-agent access events. |
| memory_recentA | Newest shared records from any agent, in brief form: summary, files, open threads with
their ids, and a details preview. Words in |
| memory_recordA | Persist a completed unit of work into immediate ASM memory and the Obsidian daily log. Call after changing files. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The six brain_* query tools are semantically distinct (search vs. node lookup vs. neighbors vs. path vs. file context), and the two memory_* tools handle read vs. write. brain_context and brain_neighbors overlap somewhat (both pull neighbors), but descriptions clarify the intended use.
All seven tools follow a strict prefix_noun/verb pattern with two clear families: brain_* (graph queries) and memory_* (shared-memory read/write). snake_case is used consistently throughout.
Seven tools is well-scoped for an ASM/knowledge-graph memory server, covering structured query (search, node, neighbors, path, context) and memory lifecycle (recent, record) without excess.
The surface covers read-side graph exploration and memory write/read, but lacks any update/edit/delete for records (only 'supersedes'/'resolves'/'corrects' fields on write) and no explicit lifecycle-management tools. A create+read pattern without standalone mutation tools is a notable gap.