Booboo
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| booboo_statsA | Node/link counts for the whole graph, broken down by layer. |
| booboo_searchA | Search nodes by label or id (ranked: exact > prefix > substring). Use this first to find a node's id. |
| booboo_nodeC | Fetch a single node (all fields + data) by its exact id. |
| booboo_countA | Aggregate: filter the graph, then group and count. Use for 'how many', 'top N', 'most/least' and any date-window question — search ranks, this counts. e.g. major incidents in a date window: {type:'observation', where:{'data.kind':'incident','data.severity':'major'}, since:'2026-07-12'}; the biggest absence offender: {where:{'data.kind':'absence'}, groupBy:'data.subject'}. |
| booboo_neighborsB | The neighbourhood around a node: connected nodes + links out to |
| booboo_pathB | Shortest path (chain of nodes) between two node ids; null if unreachable. |
| booboo_rememberA | Persist a memory to the brain — one durable, atomic fact/decision worth recalling later. Written to the append-only journal beside the snapshot; immediately queryable and survives every rebuild. Author |
| booboo_reportA | File a report — a plain-English summary of what an agent just closed. Lands on the panel's Reports timeline; durable and immediately queryable. Call this as the last act of a session. |
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 8 tools
Most tools have clearly distinct purposes, but booboo_stats and booboo_count both provide counting functionality. Stats gives whole-graph layer counts, while count allows filtered and grouped aggregations, reducing ambiguity but still potentially confusing at first glance.
All tools use the consistent 'booboo_' prefix, but the suffixes mix nouns (stats, node, neighbors, path) and verbs (search, count, remember, report). This inconsistency prevents a predictable verb_noun pattern, though the names remain readable and understandable.
With 8 tools covering graph statistics, search, fetching, aggregation, neighborhood traversal, pathfinding, memory persistence, and reporting, the count is well-scoped for the server's purpose without being excessive or insufficient.
The tool surface covers the primary graph query and persistence workflows well, including search, single-node retrieval, neighborhood analysis, pathfinding, and durable writes for memories and reports. Minor gaps exist, such as no explicit update/delete for persisted items and no way to list all nodes without a search query, but these are workable within the intended domain.