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": true
}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
handoff_createB

Leave a task for another agent working on this project, addressed to its agent label, such as reviewer, or to * for any agent. Returns the handoff's id.

handoff_doneB

Mark a handoff you took as done, with an optional note on what you did.

handoff_listA

List this project's handoffs addressed to you or to any agent, open ones unless state says otherwise. mine lists the ones you created instead.

handoff_takeA

Take an open handoff addressed to you or to any agent, by its id, and read it in full. Only one agent can take a handoff.

memory_readA

Read one saved note in full by its id.

memory_searchA

Search the notes agents have saved for this project. Returns ids, titles and snippets, best matches first.

memory_writeA

Save a note for the other agents working on this project: a decision, a finding, a convention. Returns the note's id. Pass supersedes to replace an older note.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

The seven tools split cleanly into two non-overlapping domains (handoffs and memory notes), and within each domain the operations target distinct lifecycle stages. handoff_create/take/list/done are unambiguous, and memory_read (by id) versus memory_search (by query) are clearly differentiated.

Naming Consistency4/5

All names use a predictable snake_case namespace_verb pattern (handoff_*, memory_*), which is easy to scan. The only minor wrinkle is handoff_done, which is a state adjective rather than a verb like the others, but consistency overall is strong.

Tool Count5/5

Seven tools is a well-scoped set for a coordination server: four handoff operations and three memory operations, each earning its place. Nothing is redundant or missing at the count level.

Completeness4/5

Coverage is solid: handoffs support create/list/take/done, and memory supports write/read/search plus supersedes for replacement. Minor gaps remain (e.g., no delete or list-all for memory notes, no cancel/release for a taken handoff), but agents can work around these.

Maintenance

ActivityMaintained
ResponsivenessNo issues