brainy
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BRAINY_DB_PATH | No | Path to the SQLite database file | |
| BRAINY_KNOWLEDGE_ROOT | No | Path to the knowledge repository root | |
| BRAINY_WORKER_PLUGINS | No | Worker plugins to load (e.g., Claude Code, Codex) | |
| BRAINY_PUBLIC_BASE_URL | No | Public base URL for remote AI connectors (HTTPS URL) | |
| BRAINY_WEB_SESSION_KEY | No | Path to the web session key file |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| append_documentC | Append to an allowed target (e.g. shared/todo.md). |
| approve_taskA | Approve the approval gate (-> APPROVED). Requires approve permission; no self-approval. |
| claim_taskC | Claim a task atomically (lease + claim_token). |
| complete_taskB | Complete a task — governance-gated (AUTO->COMPLETED, REVIEW->AWAITING_REVIEW, APPROVAL->AWAITING_APPROVAL). |
| create_taskD | Create a task. |
| disable_agentC | Disable an agent (ADMIN). |
| enable_agentB | Enable an agent (ADMIN). |
| fail_taskC | Mark a task as failed (idempotent). |
| get_agent_statusC | Status of an agent. |
| get_documentB | Read a knowledge document (path allowlist, ACL). |
| get_execution_jobB | Read an execution job (without dispatch_token). |
| get_taskC | Read a task. |
| list_agentsB | List the agent registry (no secrets). |
| list_documentsC | List canonical Markdown documents (optional space). |
| list_execution_jobsC | List execution jobs (without dispatch_token). |
| list_runnable_tasksB | Tasks runnable by this principal (READY, deps satisfied, ACL, required_capabilities, preferred_agent). |
| list_spacesB | List visible knowledge spaces. |
| list_tasksC | List tasks of a readable space. |
| pause_dispatcherA | Pause the dispatcher globally (ADMIN, kill switch). |
| propose_writeA | PROPOSE a change to a knowledge document (no direct write). The owner approves via Telegram; only then is it committed. Use this when you do not have direct write permission. |
| reject_taskA | Reject at the approval gate (-> REJECTED). Requires approve permission. |
| release_taskC | Release your own claim. |
| renew_claimC | Extend the lease. |
| resume_dispatcherA | Resume the dispatcher globally (ADMIN). |
| review_taskB | Decide the review gate (decision=accept|reject). Requires review permission; no self-review. |
| search_knowledgeC | Search knowledge case-insensitively (ACL, optional space). |
| write_documentC | Write a knowledge document (git commit; ACL/secret guard). |
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 27 tools
Each tool targets a distinct resource+action: the task lifecycle verbs (claim/complete/fail/approve/reject/review/release/renew) are well differentiated by their governance roles, and document tools (write/append/propose/search) are clearly separated. Only mild potential confusion exists between the various task gate tools, but descriptions clarify intent.
Every tool follows a strict verb_noun snake_case pattern (list_agents, create_task, claim_task, write_document, pause_dispatcher), with predictable verbs for read/list/create/mutate operations. No convention mixing is present.
27 tools is on the heavy side and exceeds the comfortable 3-15 range. However, the surface spans five legitimate subdomains (tasks, documents, agents, execution jobs, dispatcher), so the count is defensible rather than bloated.
Task and document lifecycles are well covered (create/claim/complete/fail/approve/reject/review plus read/write/append/search/propose). Execution jobs are read-only (get/list with no create or claim path) and no delete operations exist, which are minor workable gaps.