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

Tools

Functions exposed to the LLM to take actions

NameDescription
runB

Launch an instructed agent. Sessions return only when reachable; tasks return a non-messageable run handle.

listA

List Muster-owned sessions and tasks, including host capabilities.

stopA

Stop a Muster-owned run by durable id or unambiguous peer name.

outputC

Read captured output from a task run.

titleB

Retitle a running tmux session by durable id or unambiguous peer name, from outside its agent.

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 5 tools

Disambiguation5/5

Each tool targets a distinct lifecycle action: run launches, list enumerates, output reads, title renames, and stop terminates. Overlap is minimal, with output and list only differing by scope.

Naming Consistency5/5

All tool names are lowercase single-word commands (run, title, list, output, stop), giving a consistent imperative style. No mixed conventions or prefixes/suffixes are present.

Tool Count5/5

Five tools is compact and appropriate for a session/task orchestration server, covering launch, inspection, output retrieval, naming, and termination without redundancy. No obvious over- or under-scoping.

Completeness4/5

The surface covers the core lifecycle: launch (run), list/inspect (list), read output (output), rename (title), and stop. It may lack a direct message/send tool for interacting with reachable sessions, but core operations are present.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive