Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchA

Search this machine's memory of the repo: past agent sessions, commits and code structure. Every result names where it came from.

Work another agent has claimed is withheld: you get who holds it, not
the answer. Ask them, or pick up something else. If you genuinely must
have it, call again with `override` set to your reason, which is
recorded in the journal against your name.

`on_behalf_of` names a teammate when the agent is working for one. They
see only the folders they were actually shared, and nothing else.
aboutA

What is known about one thing: a file, a person, a topic.

rememberA

Write something back, so the next session in any agent knows it too.

Set `claiming` when you are about to start work on this, rather than
just noting something. Other agents are then told you have it and knos
withholds it from them until you finish or half an hour passes. Writing
a plain fact claims nothing: a note everybody can read is the point.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation4/5

search and about both query stored knowledge, so an agent could initially confuse a broad search with an entity-focused lookup, but the descriptions make the distinction clear: search returns provenance-backed results from repo memory, while about targets one thing. remember is wholly separate as a write operation.

Naming Consistency4/5

All tool names are lowercase single words, creating a simple and consistent style; search and remember are clear verbs, while about is more of a query noun/preposition, slightly deviating from a strict verb pattern.

Tool Count5/5

Three tools is well-scoped for a focused memory/knowledge server: query broadly, query a single entity, and write back. Each tool has a distinct role and none feel redundant or missing at this level of abstraction.

Completeness4/5

The core read/write/query lifecycle for shared repo memory is covered, and claimed work handling is integrated into search and remember. Minor gaps exist around updating or forgetting explicit memories, but agents can work around these with search.

Maintenance

ActivityActive
ResponsivenessWithin a week