io.github.pmaxx2023/handoff-kit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_handoffB | Build a task handoff record (task, done, evidence, failed, unknowns, next_step) and seal it with a sha256 receipt so the next agent can confirm it was not altered. |
| validate_handoffC | Score a handoff's completeness, flag unverified claims, check any existing receipt, and issue a fresh receipt. |
| merge_handoffC | Merge two handoffs into one sealed record linking both as previous. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
The three verbs—create, validate, merge—map to mostly distinct operations on handoff records. There is slight overlap because create and merge both produce sealed records, and validate also issues a fresh receipt, but the primary actions remain clear.
All tools follow the same snake_case verb_handoff pattern: create_handoff, validate_handoff, merge_handoff. The noun and imperative verb style are fully consistent.
Three tools are well-scoped for a narrow handoff-record workflow. Each tool covers a distinct stage—creation, validation, and merging—without redundant surface area.
The surface covers the core handoff lifecycle: create, validate, and merge with receipt handling. It lacks an explicit read/list/retrieval tool for existing handoffs, but the likely stateless design makes this a minor gap rather than a blocker.