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
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
record_eventB

Record a bounded significant event. Full transcripts should not be sent here.

record_failureC

Record a bounded failure signal.

record_correctionD

Record a bounded correction signal.

reflectC

Create a candidate lesson from evidence events.

validateC

Validate a lesson candidate and enqueue approved lessons for promotion.

process_promotionsC

Process pending validated lessons and promote passing items.

retrieveC

Retrieve policy-first, stage-aware lessons.

report_outcomeC

Report telemetry for a retrieved lesson.

get_policiesB

Return active policies visible to a namespace.

add_policyC

Add a local policy rule.

add_skillC

Add a reusable skill/workflow block.

search_skillsC

Search reusable skills visible to a namespace.

get_skillA

Read a reusable skill by ID.

learn.run.startD
learn.run.eventD
learn.run.endD
learn.storeD
learn.retrieveD
learn.reflectD
learn.validateD
learn.evaluateD
learn.feedbackD
learn.improvementsD
learn.analyticsD
learn.policiesD
learn.experimentD
learn.rollbackD
learn.skillsD
learn.telemetryD

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
policies_resourceActive global policies.

TDQS

D1.7/5.0

Scored across 29 tools

Disambiguation2/5

Many tools have overlapping or ambiguous names, especially the 'learn.*' tools with empty descriptions (e.g., learn.analytics, learn.evaluate) which are indistinguishable from each other. Additionally, 'retrieve' and 'learn.retrieve' appear to serve similar purposes, causing confusion.

Naming Consistency2/5

Naming conventions are mixed: some use underscore (add_policy), some use dot notation (learn.analytics), and some are single words (reflect). The 'learn.' prefix is applied inconsistently across tools, and verb_noun patterns are not uniformly followed.

Tool Count2/5

29 tools is excessive for a server that appears to manage policies, skills, and lessons. Many tools seem redundant (e.g., multiple learn.* tools) and could be consolidated. The scope does not justify this many distinct operations.

Completeness3/5

Core functionalities like adding, retrieving, and validating are present, but there are missing operations such as updating or deleting policies/skills. The learn.* tools are undocumented, leaving potential gaps in the learning pipeline unaddressed.

Maintenance

ActivityInactive
ResponsivenessUnresponsive