Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BRAINFORGE_VAULTNoThe path to the wiki vault directory (e.g., ~/my-brain/wiki). This can be set via the --vault command-line argument or as an environment variable.

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
explain_nodeC

노드의 상세 정보와 연결 관계를 조회한다. 노드 이름이나 ID의 일부를 입력하면 해당 노드의 카테고리, 파일 경로, 태그, 나가는/들어오는 엣지 목록을 반환한다.

find_pathB

두 노드 사이의 최단 경로를 BFS로 탐색한다.

causal_chainC

특정 노드와 관련된 모든 인과 관계를 조회한다.

graph_summaryB

현재 위키 그래프의 전체 요약 통계를 반환한다.

rebuild_graphB

위키 마크다운을 파싱하여 그래프를 재빌드한다.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: causal_chain retrieves causal relationships, explain_node provides node details, find_path finds paths between nodes, graph_summary gives overall statistics, and rebuild_graph rebuilds the graph. An agent can easily tell them apart based on their specific functions.

Naming Consistency5/5

All tool names follow a consistent snake_case pattern with clear verb_noun structures (e.g., causal_chain, explain_node, find_path, graph_summary, rebuild_graph). The naming is uniform and predictable throughout the set.

Tool Count5/5

With 5 tools, the count is well-scoped for a wiki graph management server. Each tool serves a distinct and necessary function, covering key operations like querying, explaining, pathfinding, summarizing, and rebuilding without being excessive or insufficient.

Completeness4/5

The tool set provides strong coverage for core wiki graph operations, including querying nodes and relationships, pathfinding, and graph maintenance. A minor gap exists in update or delete operations for nodes or edges, but agents can work around this using rebuild_graph for modifications.

Maintenance

ActivityInactive
ResponsivenessNo issues