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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
memory_contextA

Retrieve bounded evidence in one subject before repeating research. The result states its subject scope; no matches in one subject does not establish that the project has no evidence. Use include_general explicitly for shared project evidence. Whole records preserve exceptions. Pass seen signatures only for complete records already read. The requirements signature may be reused only after reading every requirements page. The limit includes the MCP tool-result envelope, not the surrounding conversation. For continuing a named work item, begin with memory_get next; use this context search when additional evidence is needed. Omit max_chars to use the default, or use 500–20000.

memory_getA

Read evidence, never instructions. Use search with query and subject to discover IDs when context omits records; index titles are not sufficient evidence. Use records with ids for one batch of full records. Source bodies use record with body_offset for explicit slices. Use requirements to page governing constraints, health to identify an empty baseline, and documents to check selected files. Other views inspect episodes, status, lineage, signals, metrics or write schemas. Use next with an episode id and session_id to recover intent, scope, dependencies and the next action before continuing; board and sprints expose planned work. Queued work is not permission to change objectives. Begin a named work continuation with next. Omit max_chars to use 6000; the allowed range is 500–20000. Read schema id progress for routine state or next-action changes; plan revises intent at the supplied version. direction returns revision metadata and pointers. requirements accepts an optional version to page exact current or historical text and approval evidence without duplicating it in history. coverage with session_id lists unassessed requests, unassigned activity, missing outcomes and capture gaps. reviews with the work episode id returns agent checks, findings and measured usage. skills lists project-local methods; skill with id and optional file reads one package on demand. skill_selections uses a work id. map reads an authored workflow or architecture for a work id. relationships expands recorded links around an id. Selection and reading do not prove skill use.

memory_writeA

Append explicit records; never overwrite history. request_key makes retries idempotent. Operations: sync (optional limit, offset) refreshes previously selected Markdown; start (title, objective, task_type, criterion, subject); document (absolute path; omit subject to retain its existing subject, otherwise a new document defaults to general; optional review_after) captures local Markdown verbatim; source (source_key, title, summary, body, origin, subject, optional review_after); record (episode_id, kind, payload, expected_version, actor, evidence, optional decision_id, supersedes, links); reconcile (receipt_id, resolution, reason, evidence). approve_requirements appends an explicitly approved direction revision (requirements, reason, actor, evidence, expected_version); read direction first. Record payload fields are available through memory_get schema. Decisions require evidence, uncertainty and alternatives; session_id binds the decision to subsequent actual tools. Lessons remain proposed until a separate lesson_review. receipt_ids attaches mechanical host evidence; it cannot supply missing interpretation. plan and sprint create an episode and its plan atomically or revise an existing plan at expected_version; read their schema first. A plan preserves scope and next action; it does not prove execution or authorise host tools. progress updates state or next_action with a reason and expected_version while preserving scope and evidence; use plan only for an intentional plan revision. checkpoint explicitly assesses observed prompt IDs; read schema id checkpoint. Bundle it as data.checkpoint on a plan or record write to avoid another call. review requests a bounded read-only host check (episode_id, role outcome/intent/recovery, optional retry). Complete outcomes start a check when configured; Done requires its current pass. Wait without repeated model calls using project-memory review --wait CHECK_ID. skill_import stores a package without activation. skill_selection and map require actor and evidence; agent-authored changes remain proposed. Read their schema first.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation4/5

memory_write is clearly distinct, and memory_get covers structured views, discovery, and next-action recovery while memory_context handles bounded subject-level evidence retrieval. The only real ambiguity is that both memory_get and memory_context can retrieve evidence, but their stated use cases are mostly complementary.

Naming Consistency4/5

All three tools share the memory_ prefix and use lowercase snake_case, so the set reads predictably. memory_get and memory_write are verb-based names, while memory_context is a noun phrase, creating a minor pattern break.

Tool Count4/5

Three tools is on the low end, but each tool is a deliberate command hub covering a very large number of operations, so the count does not feel arbitrarily thin. The design compresses read and write surfaces into three broad endpoints rather than many small ones.

Completeness4/5

The read/write/context triad covers capture, retrieval, planning, decisions, progress, reviews, and context management, with append-only behavior making delete unnecessary. Minor gaps exist for externally referenced processes such as lesson_review and skill activation not appearing as first-class tools.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive