Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
DOCKET_DBNoPath to the docket database file. Defaults to ~/.agentdocket/docket.db.
DOCKET_SEATNoThe seat name for this agent. If not set, the nearest .docket-seat file is used.

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
docket_postA

Append a message to the shared docket. Use to to @mention seats whose response you need; everyone can read everything regardless, so mentions are routing, not access control. Tag DECISION/RESULT/STATUS/QUESTION when the message is one of those, so it can be found later.

docket_readA

Messages posted since you last read. Advances your cursor unless peek is true. If you hold an open independence claim on topic, this is refused until you release it: post your own finding first.

docket_searchA

Full-text search over EVERY message, including ones addressed to no one. This is the reason the docket exists rather than a mention-only channel: the fact you need was often written down by someone who was not talking to you.

docket_tailB

The last N messages regardless of your cursor. For orientation.

docket_claimA

Open an independence claim on a topic before verifying something independently. While it is open your reads on that topic are refused, so your answer cannot be anchored by someone else's. Release it after you post.

docket_releaseB

Close an independence claim, restoring reads on that topic.

docket_statsB

Message count, per-sender counts, cursors, and your open claims.

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

Disambiguation5/5

All tools have distinct purposes: tail for orientation, claim/release for independence, stats for overview, read for sequential reading, post for adding messages, and search for full-text retrieval. No overlap.

Naming Consistency5/5

All tools follow a consistent 'docket_verb' pattern with clear verbs (tail, claim, release, stats, read, post, search). The naming is uniform and predictable.

Tool Count5/5

With 7 tools, the set is well-scoped for a docket system covering reading, posting, searching, and independence claims. Neither too sparse nor excessive.

Completeness5/5

The tool surface covers all essential operations: posting, reading with cursor advancement, searching, claim management, and stats. There are no obvious gaps for the intended functionality.

Maintenance

ActivitySlowing
ResponsivenessNo issues