Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENAI_API_KEYNoAPI key for real model answers. Optional if using deterministic fake backends.
STIGMERGY_REPOYesPath to the knowledge repository (git checkout).

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_brainB

Search ACL-visible team knowledge with hybrid ranking.

read_pageB

Read one ACL-visible wiki page.

list_entitiesA

List entity identities visible to the current reader.

describe_entityC

Return a bounded, ACL-visible entity dossier with cited relationship evidence.

askB

Answer from ACL-visible team knowledge with citations.

brain_submitA

Submit exactly one text value, local file path, or URL to the team wiki.

An explicit resolution_of target remains subject to the cloud writer's evidence and ACL gates.

brain_submissionsA

List queued, processing, landed, or failed submissions.

brain_deleteC

Queue an authorized explicit page or source deletion.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 8 tools

Disambiguation4/5

Most tools target clearly distinct actions: searching, reading pages, listing/describing entities, submitting, tracking submissions, and deleting. The main ambiguity is between search_brain and ask, since both query team knowledge and return cited results, though one is search-oriented and the other is answer-oriented.

Naming Consistency3/5

The set mostly uses readable snake_case verbs like read_page, list_entities, and describe_entity, but also includes bare 'ask' and the reverse-prefixed brain_submit, brain_submissions, and brain_delete. This creates a mixed convention that is still understandable but not fully consistent.

Tool Count5/5

Eight tools is well-scoped for a team knowledge/wiki server. Each tool maps to a meaningful operation without redundancy or bloat.

Completeness4/5

The set covers searching, reading, entity discovery, questioning, submitting content, tracking submissions, and deleting content—a solid lifecycle for this domain. Minor gaps exist, such as no explicit page/entity update tool or detailed submission inspection beyond status listing.

Maintenance

ActivityNo data
ResponsivenessResponsive