closure_drift
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 |
|---|---|
| check_versionsB | Does each version label in this git repository name exactly one code state across its tags? Read-only. |
| would_tagA | Run BEFORE creating a release tag: would HEAD reuse a version label that already names other code? Read-only. |
| explain_labelB | List the paths that differ under one version label found in drift. Read-only. |
| compareB | Compare two tags or commits: their version labels, closures and the paths that differ. Read-only. |
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 4 tools
Each tool has a distinct read-only purpose: repository-wide label check, HEAD preflight, per-label path explanation, and two-ref comparison. However, explain_label and compare both list differing paths, and would_tag is a specific case of check_versions, creating minor overlap.
All names use snake_case, but the verb patterns are mixed: check_versions and explain_label follow verb_noun, compare is a bare verb, and would_tag is an unusual modal_verb construction. The inconsistency is noticeable though names remain readable.
Four tools is well-scoped for a specialized read-only drift-analysis server; each tool covers a distinct analysis step (bulk check, preflight, explain, compare) and none feels redundant.
The set covers the core drift-analysis workflow: detect drift, preflight a tag, investigate a drifting label, and compare refs. A minor gap is the lack of a standalone tool to list all version labels or inspect a single non-drift label's closure.