Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COMMANDER_PLUS_HOMENoSet to move the local state directory.

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
}

Tools

Functions exposed to the LLM to take actions

NameDescription
workspace_registerC

Register a local project workspace.

workspace_listB

List registered local workspaces.

skill_saveC

Save a reusable skill with routing metadata.

skill_routeC

Rank locally saved skills against a task intent.

guardian_workspace_healthA

Check whether registered workspace roots remain readable.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.2/5.0

Scored across 5 tools

Disambiguation4/5

Workspace register vs list are clearly paired but distinct, and skill_save vs skill_route are clearly separated by action. The only slight ambiguity is between workspace_list and guardian_workspace_health, which both report on registered workspaces from different angles (enumeration vs readability).

Naming Consistency4/5

All names are snake_case verb_noun style (workspace_register, skill_save, skill_route) which is predictable. The outlier is guardian_workspace_health, which uses a subsystem prefix rather than a verb, breaking the pattern for that one tool.

Tool Count4/5

Five tools is a compact, well-scoped set for workspace registration plus local skill routing, with no filler. It sits slightly on the thin side, particularly on the skill side where a single save/route pair carries the whole capability.

Completeness3/5

There is save and route for skills but no skill list, update, or delete, and workspace_register has no corresponding unregister/remove counterpart. The surface covers the happy path but leaves obvious lifecycle gaps an agent would hit when managing or cleaning up entries.

Maintenance

ActivityStale
ResponsivenessNo recent community issues